The whole reason was working in the browser.
WPF was great for desktop, albeit Windows only.
So that was wrecked after .net framework became .net core (and thus needed crossplatform).
Then some shitheads at Microsoft got the “release new UI framework to get a promotion” annual bug: winui, maui, etc.
All that instead of making WPF crossplatform.
That’s why C# succumbed to server API only (and games of course, but those blokes suffer as most great C# features are not supported in Unity).
That was the grandeur of Windows Vista: not the OS but completely new dev stack (wpf, linq, wcf, etc.) that was feature rich for a few decades to come. And they fucked most of it up instead of building further on the same foundation.
And after you keep abandoning the technologies devs will say FU and go to something more stable to build a business.
Even now, .net is keep getting rewritten (meaning existing features being abandoned) because board wants those sweet-sweet money from the cloud functions and what have you instead of you being self-hosted and not vendor-locked
> All that instead of making WPF crossplatform.
Avalonia (https://avaloniaui.net/) and Uno (https://platform.uno/) are cross platform UI frameworks for .NET.
Both work in the browser with WebAssembly. Avalonia renders to canvas. Uno can render to canvas or the DOM. Here are a couple of Avalonia demos:
https://solitaire.xaml.live/
https://bandysc.github.io/AvaloniaVisualBasic6/