5 ms·
If anyone from MS is reading this, please consider throwing some support behind WPF. It's actually a very reasonable framework for native development, and with
by avinium 9y ago
If anyone from MS is reading this, please consider throwing some support behind WPF. It's actually a very reasonable framework for native development, and with a few updates here and there, would be competitive (in terms of developer-hours) with the latest JS frameworks.
I doubt that will happen, as MS is seemingly embracing the whole web-services/HTML/JS model. VS Code might be the nail in the coffin - possibly an Electron test-case to see if the entire VS proper can be ported over.
- pjmlp 9y agoFuture of WPF is UWP. WPF is for pre-Windows 10 desktops.
- martinsuchan 9y agoAdding Compiled Bindings to WPF could be a nice start.
- mattmanser 9y agoI remember when I learnt Silverlight it had a huge learning curve because Xaml takes a while to wrap your head around. Given that, I can't really see it ever becoming competitive.
- taspeotis 9y agoThere's a glimmer of hope over here [1]. Microsoft updated the XAML Designer. The new designer has support for UWP but note the comments. In particular "WPF [support] will be shipped sometime after the UWP Designer has been released and stabilized." [1] https://blogs.msdn.microsoft.com/visualstudio/2017/09/11/a-significant-update-to-the-xaml-designer/ https://blogs.msdn.microsoft.com/visualstudio/2017/09/11/a-s...