-
Notifications
You must be signed in to change notification settings - Fork 408
Closed
Labels
Feature-Up-to-dateBuild up-to-date check that avoids shelling out to MSBuild unless necessary.Build up-to-date check that avoids shelling out to MSBuild unless necessary.Resolution-No-ReproWe cannot reproduce the bug. We need more information, clearer repro steps or a sample project.We cannot reproduce the bug. We need more information, clearer repro steps or a sample project.
Description
I am trying to get the new 2017 csproj-Format working with our WPF and WinForms projects. The problem is that Visual Studio modifies the csproj-File after adding a new file.
Steps-to-reproduce:
- Open the attached project
- Add a new xaml-file
Expected behavior:
- Visual Studio does not touch the csproj-File (as there is already a rule for xaml files)
Actual behavior:
- Visual Studio adds two new ItemGroups:
<ItemGroup>
<None Remove="UserControl1.xaml" />
</ItemGroup>
<ItemGroup>
<UpToDateCheckInput Remove="UserControl1.xaml" />
</ItemGroup> - Therefore the xaml is not displayed correctly in the Solution Explorer. After restoring the unmodified csproj everything looks good again
_This issue has been moved from https://developercommunity.visualstudio.com/content/problem/238439/visual-studio-modifies-csproj-file-when-adding-xam.html
Metadata
Metadata
Assignees
Labels
Feature-Up-to-dateBuild up-to-date check that avoids shelling out to MSBuild unless necessary.Build up-to-date check that avoids shelling out to MSBuild unless necessary.Resolution-No-ReproWe cannot reproduce the bug. We need more information, clearer repro steps or a sample project.We cannot reproduce the bug. We need more information, clearer repro steps or a sample project.