3 ms·
Adding to what ripley said, there's never been a great (FOSS) ecosystem of WPF libraries. By now half of them haven't been updated since 2012 and half of those
by mastax 5y ago
Adding to what ripley said, there's never been a great (FOSS) ecosystem of WPF libraries. By now half of them haven't been updated since 2012 and half of those have bugs if you try to use them in .NET 5+.
- tonyedgecombe 5y agoIt's not surprising, Microsoft seemed to abandon it at birth. If Microsoft can't be bothered then why should anybody else.
- int_19h 5y agoVisual Studio still has large parts of its UI written in WPF.
- tonyedgecombe 5y agoThat's a good example. Where is the property grid in WPF, a component that is central to Visual Studio's UI.
- int_19h 5y agoVisual Studio has bits and pieces written in pretty much all UI frameworks that Microsoft ever had - at some point there were even HTAs there, not sure if that's still the case. Some bits get rewritten, like the main window chrome / menus / toolbars (all WPF now). Some do not. That said, as I recall, the property editor that you get when editing WPF controls and forms is itself WPF these days. But anyway, my point is that it was hardly "abandoned at birth", given that WPF was originally released with .NET 3.0 in 2006, while the first version of VS to get WPF UI was VS 2010 - and more was rewritten since then. Even if no new VS components are ever going to be written in it, maintaining the existing ones makes it necessary to maintain WPF to some bare minimum standard. (The same goes for WinForms and other UI stacks that VS still uses in places.)
- tonyedgecombe 5y agoVisual Studio might well have used it but the point was what happened to WPF since it was released. Almost nothing. It wasn't complete when it was launched and has never really been updated in a significant way.