You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows Community Toolkit 8.2 is slated to release soon, with 8.2-preview2 already in flight.
Problem
To facilitate a smooth release, we need to ensure that the gallery app published to https://apps.microsoft.com/detail/9nblggh4tlcq is updated with the lates source, samples and docs from 8.2.
Solution
Build the UWP gallery app in release mode.
Run through the app in Release mode, evaluate for possible regressions
File tickets for any regressions found
Publish to the Microsoft Store
UWP or Wasdk?
With how much code is in the toolkit, .NET Native takes significant time and resources just to build release, let alone debugging building release.
We can't publish UWP with .NET 9 to the Microsoft Store due to the NativeAOT requirement, but we could publish Wasdk with NativeAOT disabled.
It was discussed that we may try publishing the Wasdk version of our Gallery app without NativeAOT, if UWP gives us persistent troubles.
Which we end up doing ultimately depends on how much time we're forced to waste wrestling with .NET Native.
The text was updated successfully, but these errors were encountered:
Tried updating the analytics PR from before (no updates to the package, following up on that with Sergio to see if he can find out who in Store owns that now). See PR #206.
I'm not sure why it fails to build with a binary conflict though in the CI. I haven't had issues in the past with it building locally, but forgot to add it for 8.1, I think.
Background
Windows Community Toolkit 8.2 is slated to release soon, with 8.2-preview2 already in flight.
Problem
To facilitate a smooth release, we need to ensure that the gallery app published to https://apps.microsoft.com/detail/9nblggh4tlcq is updated with the lates source, samples and docs from 8.2.
Solution
UWP or Wasdk?
With how much code is in the toolkit, .NET Native takes significant time and resources just to build release, let alone debugging building release.
We can't publish UWP with .NET 9 to the Microsoft Store due to the NativeAOT requirement, but we could publish Wasdk with NativeAOT disabled.
It was discussed that we may try publishing the Wasdk version of our Gallery app without NativeAOT, if UWP gives us persistent troubles.
Which we end up doing ultimately depends on how much time we're forced to waste wrestling with .NET Native.
The text was updated successfully, but these errors were encountered: