Now that we've released Uno 5.0, it makes sense to move to WinUI first, since most of our users are using it. And it's going to make Uno devs happy!

A PR of 5000+ files is going to be fun to review! It's for a good cause, though. Uno has been using the UWP API as its base source from the beginning, and a CI time conversion to create WinUI compatible packages... (1/2)

At least you're able to build all of it with a `dotnet build`, right? No juggling with msbuild and dotnet build.

Hello Bluesky! I’m the CTO @unoplatform.bsky.social#dotnet#csharp#webassembly and mobile dev, among other things. I just got in via an organic invitation, eager to see how this is different from mastodon… Is there anything I should know about this platform?