-
Notifications
You must be signed in to change notification settings - Fork 70
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
Upgrade to .NET 7, enable WASM optimizations #173
Conversation
Local packages were built for this branch tested to work on these platforms:
Android Runtime error, see details.
|
27e89fd
to
5e19e64
Compare
Kicked off a new build, hopefully the package versioning stuff is all resolved, so we'll have a clean set of new packages to try soon! 🤞 |
51386df
to
4945f73
Compare
Build good, but have been having trouble with the uno template from VS on my machine, trying in VS Code now. Got this message from NuGet about the android package:
Do we have to be more specific than |
Was able to test in VS Code from the command line with |
Tested the We can probably remove the |
Found some useful information about how Uno handles net6 and net7 targets on Android: unoplatform/uno#11423 I'll switch us over to android33.0 for now and trying that while waiting for a reply. |
c5eaae2
to
67751cc
Compare
Looks like these are the last warnings hopefully:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nit, and something to follow-up on later, but otherwise we should be good. Yay!
Did these not need to be addressed too though? #173 (comment)
Update tooling to latest upgrade/net7
Cleaned up some logic for diagnostic builds as well so we have a single build command
2023-08-17T20:08:53.7233918Z 5>D:\a\Windows\Windows\components\Behaviors\src\Notification\StackedNotificationsBehavior.cs(16,70): error CS1574: XML comment has cref attribute 'InfoBar' that could not be resolved
0f881a6
to
7328b98
Compare
Companion PR to CommunityToolkit/Tooling-Windows-Submodule#117, which should be closed before merging this.
As noted:
This PR pulls in the .NET 7 upgrade and fixes the new warnings and errors that appeared in our codebase as a result.