Skip to content

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

@dhoehna

Description

@dhoehna

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions