-
Notifications
You must be signed in to change notification settings - Fork 719
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
When adding a new page via copy-paste, the csproj adds ItemGroups that makes the new page uncompilable #16605
Comments
Thanks for the report. This looks similar to dotnet/project-system#7028 (/cc @dansiegel) |
@jeromelaban, @dansiegel
|
@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. |
@jeromelaban Video of my steps https://github.com/unoplatform/uno/assets/1608424/2011549b-d239-4a0c-bfed-93e0bc191e69 In words:
|
Adding a new UserControl via Add New Item also create noises in csproj |
The key comment is dotnet/aspnetcore#24790 (comment), where :
It looks like we should be avoiding including files in multiple item groups, but that seems counter inuitive for some scenarios, particularly |
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 |
What would you like clarification on
In this article, it should be mentioned that when adding a new page, the developer needs to manually remove the ItemGroup added in the csproj.
These ItemGroups generate the compilation error "XYZPage does not contain a definition for 'InitializeComponent' and no accessible...
Concern
Developing with Uno
Affected platforms
Windows (WinAppSDK)
Any feedback?
No response
The text was updated successfully, but these errors were encountered: