Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug where WPF temp project is not handled correctly. #379

Open
dhoehna opened this issue Mar 3, 2025 · 1 comment
Open

Bug where WPF temp project is not handled correctly. #379

dhoehna opened this issue Mar 3, 2025 · 1 comment

Comments

@dhoehna
Copy link

dhoehna commented Mar 3, 2025

When building WPF, a new, temp project is made and the project name ends with _wpftmp.

The bug is CPS does not copy all the files over to the temp project causing a build failure.

The bug appears when using CPS and the project has at least one User Control.

Microsoft.VisualStudio.ProjectSystem.Sdk.Tools.targets line 29 adds a target to handle moving the files to the new project but the files are not moved over.

The project system does have a workaround. I added this to my project. Still an issue.

Repro steps:

  1. Make a new project using the CPS's Project Type template. Use the default values the wizard gives.
  2. In the [NewProjectName].ProjectType project add a WPF UserControl
  3. Rebuild [NewProjectName].ProjectType
  4. Build fails because ScriptDebugger can't be found in the temp project.

In this state, ScriptDebugger has odd behavior.
On clean only, ScriptDebuggerr.cs is generated in the intermediate location, as expected. Further, developers can F12 to this class.
On Build or Rebuild the file is removed and build fails because the build can not find ScriptDebugger.cs

@dhoehna
Copy link
Author

dhoehna commented Mar 3, 2025

@adrianvmsft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant