When adding a new page via copy-paste, the csproj adds ItemGroups that makes the new page uncompilable about uno

[jeromelaban]

Thanks for the report. This looks similar to dotnet/project-system#7028 (/cc @dansiegel)

[jeromelaban]

It feels like there's something incorrect in VS, let's continue tracking in https://developercommunity.visualstudio.com/t/ItemGroups-are-created-regardless-of-glo/10658677

[agneszitte]

@jeromelaban, @dansiegel
A couple more details:

• Same issue when adding a new page (without copy-paste)
• If I am not mistaken @ArchieCoder is referring to this article
  https://platform.uno/docs/articles/external/uno.extensions/doc/Learn/Navigation/HowTo-NavigateBetweenPages.html#1-navigating-to-a-new-page where it is still mentioning "(shared) project". Documentation would need to be updated as well on that aspect.

[jeromelaban]

@ArchieCoder I'm not reproducing the output you got when copying the files. Would you have more precise repro steps?

Note that Visual Studio is adding ItemGroups incorrectly for an uno app, and so does a default winui app or with a MAUI app when copying XAML files.

We'll likely need to open an issue VS community site to report it.

[ArchieCoder]

@jeromelaban Video of my steps https://github.com/unoplatform/uno/assets/1608424/2011549b-d239-4a0c-bfed-93e0bc191e69

In words:

• Create new project
• Copy paste SecondPage.xaml
• Rename SecondPage in xaml and 2 times in xaml.cs

UnoApp7.csproj.txt

[ArchieCoder]

Adding a new UserControl via Add New Item also create noises in csproj

[jeromelaban]

The key comment is dotnet/aspnetcore#24790 (comment), where :

To avoid unexpected behavior, VS is trying to avoid including a file multiple times in both None/Content.

It looks like we should be avoiding including files in multiple item groups, but that seems counter inuitive for some scenarios, particularly UpToDateCheckInput.