Re: .NET WinUi3
I'm confused, AC. Are you me? Did I accidentally write your post and then suffer amnesia?
'Cos your complaints are all exactly what I've been banging my head against my desk over, for the last week.
Having developed quite happily in WinForms for years, and WPF a little, I thought I'd keep my skills up-to-date and try WinUI3. Acrylic/Mica textures, new controls, auto scaling layouts... yum.
But as you (I?) so succinctly described, it's an absolute, unfinished train-wreck. Your post should also have mentioned the total absence of a visual UI editor within Visual Studio. Microsoft's best response at the moment is "create the UI by hand-editing the XAML, then use Hot Reload on your project to tweak the XAML and quickly see the result in the running code." <bangs head on desk again>
The cert thing is a nightmare. Microsoft's attitude is "You can build as an MSIX and battle with certs, or you can build as unpackaged, which means even the smallest Hello World takes 200MB+, and as an additional bonus 'fuck you' to our loyal devs, unpackaged projects can't use some of the system UI framework, like notifications"
I liked - hell, I like - WinForms. Easy to build a functional UI - drag and drop controls in the visual editor. Build your own user controls if needed. Quick & simple build process that creates, in most cases, a single, compact .EXE that you can copy to as many other PCs as you want & immediately run. Sure, it doesn't handle transparency well, and manual DPI scaling can be tricky if you want pixel-sharp interfaces, but it's like a familiar and comfortable pair of slippers.
To echo Knightlie's sentiment above, the fact that WinForms is still, in many ways, the best option for a project in 2023 is a damning indictment of Microsoft's utter inability to think of their developer community.
I do wish I could justify spending the $1000 for the DevExpress Winforms toolkit!