[Pre-release] v8.1.240606-rc

[michael-hawker]

What's Changed

Important Notes

• There should also be a better error message now if the wrong TFM is used by a consuming project:

• We may have noticed issues with the transitive dependencies for the Media packages (or possibly related to Animations package), if you notice issues where you need to install additional packages manually, please comment on this issue.

Highlights

• Enable AoT for net8 in Release by @Arlodotexe in Enable AoT for net8 in Release #417
• Update Uno version, Uno TFMs to .NET 8 by @Arlodotexe in Update Uno version, Uno TFMs to .NET 8 #422
• fix: Uno Platform - Avoid square border around RangeSelector Thumbs by @MartinZikmund in fix: Uno Platform - Avoid square border around RangeSelector Thumbs #400
• Fix DockPanel measuring bug by @Poker-sang in Fix DockPanel measuring bug #416

Documentation

• Update DockPanel.md by @mael8 in Update DockPanel.md #419
• Documentation fixup for v8.1 by @Arlodotexe in Documentation fixup for v8.1  #398
• Fixed remaining Microsoft Learn doc warnings by @Arlodotexe in Fixed remaining Microsoft Learn doc warnings #410

Infrastructure

• Updated actions to latest version for node 20 by @Arlodotexe in Updated actions to latest version for node 20 #387
• Fixed duplicate artifact names across matrices in CI by @Arlodotexe in Fixed duplicate artifact names across matrices in CI #411
• Fixed duplicated artifacts in CI when uploading package list by @Arlodotexe in Fixed duplicated artifacts in CI when uploading package list #421

New Contributors

• @MartinZikmund made their first contribution in fix: Uno Platform - Avoid square border around RangeSelector Thumbs #400
• @mael8 made their first contribution in Update DockPanel.md #419

Full Changelog: v8.1.240328-rc...v8.1.240606-rc

For changelog of the last 8.1-rc compared to the last stable release: https://github.com/CommunityToolkit/Windows/releases/tag/v8.1.240328-rc

---

This discussion was created from the release v8.1.240606-rc.

[nik9play]

For some reason, this RC tries to install Uno packages on the Windows platform:

The target framework is set to net8.0-windows10.0.22621.0

[michael-hawker]

That shouldn't be the case. Which package is this? Is this a UWP or WindowsAppSDK based project?

FYI @Arlodotexe

[nik9play]

This is a WindowsAppSDK based project. It happens with all packages that start with CommunityToolkit.WinUI.

[nik9play]

Well, I solved that issue. I also had to change the target framework in publish profile in addition to the project settings.

[Joost-Jens-Luminis]

For some reason it can't find the Behaviors or Converters namespace now after the update. Has that been moved or do I have to update something else as wel?

I do have the package installed:

[Joost-Jens-Luminis]

I figured it out, we were still on version 19041 for your minimum and target versions, but this has to become 22621.

[michael-hawker]

Glad you figured it out, did you see the improved error message called out above? (Did that help?)

This is one of the main upgrade issues we've noticed folks having, so we've been trying to call it out in each of our release notes.

[Joost-Jens-Luminis]

I did not see the improved error message. I double checked for you and it doesn't appear in the build output.
It might be better to set this new requirement explicitly and clearly at the beginning of the release notes. Right now it seems to be required only for the media package, but we are not using that so that causes confusion.

Also, you have to go to the What's Changed page to see this more clearly. The release notes are even less clear about this.

[Joost-Jens-Luminis]

As a result of changing the TFM to version 22621, our APP is longer installing on older windows versions (19041). We have set the TargetFrameworkVersion to 22621 but have left the SupportedOSVersion on 19041.

I saw in the release notes that this was as a result of upgrading to WindowsAppSDK 1.4/1.5, however we were already using the latest WindowsAppSDK version and were targeting TFM 19041 for the last year.

At the moment this is no longer working with this RC and as such we can no longer support any windows 10 version older then the latest one. This is causing a problem for us as some of our clients refuse or are unable to upgrade.
According to the release notes it should still work with older Windows versions without issues.

Is this behaviour intended? Can you have the SupportedOSVersion set to 19041 while the target is 22621?

[Joost-Jens-Luminis]

May I ask how you build an installer then? Maybe we are doing something wrong.

[Sergio0694]

I personally always use VS, not the command line. But regardless, have you checked the manifest in the generated package? Check the MinVersion attributes on the TargetDeviceFamily elements. Those are what should control this.

[Joost-Jens-Luminis]

Yes, and as expected for Windows.Desktop is indeed says 22621. We are not overriding this though in our pipeline so something else is. (The manifest we are providing in our solution say 19041)

[Joost-Jens-Luminis]

Looking through everything again, our Manifest file that we provide has the correct version number in it. We even make a copy of it for verification purposes (in our pipeline) so that is easy to see. I think the installer builder (MakeAppx) sets it wrong.

[Joost-Jens-Luminis]

I have found the solution. The Windows Project files requires
<TargetPlatformMinVersion>10.0.19041.0</TargetPlatformMinVersion>

The AppXManifest.xml file gets the MinVersion from this property. But with a WinUI app this property is not usually present in the .csproj file. Instead, it has the SupportedOSPlatformVersion property, however, this is not used for the AppXManifest.xml file and thus not used for the manifest of the Bundle.
Seems like a bug in .Net.
Thanks for your help on this.