Re:Deep Dive into .NET Universal Windows App Development
by _random_ on Sunday May 24, 2015 @08:03AM
(#9595994)
Is Visual Studio Code made with WPF? Is Visual Studio Online made with WPF? Is WPF open-source and multi-platform? Guess which one(s) will survive in 5 years?
Re:Deep Dive into .NET Universal Windows App Development
by ChrisLomont on Sunday May 24, 2015 @08:17AM
(#9596020)
WPF is supported as part of the OS until at the earliest 2024, and given MS ability to keep backwards compatibility longer than the web has even existed, I'm betting WPF will be the last one standing of those items you listed.
Re:Deep Dive into .NET Universal Windows App Development
by tonyedgecombe on Sunday May 24, 2015 @07:22AM
(#9595931)
If you compare the amount of activity coming out of the ASP.Net MVC team with that of the WPF team you can see why people are worried.
Re:Deep Dive into .NET Universal Windows App Development
by douche on Sunday May 24, 2015 @07:37AM
(#9595957)
The ASP.NET team is slamming things around to decouple it from IIS and Windows so that they can make a push into the server-side Linux world. ASP.NET MVC is still a relatively new technology stack, as well - three years ago I was only just thinking about getting some of our WebForms apps converted to, I believe, MVC 2.
Re:Deep Dive into .NET Universal Windows App Development
by ChrisLomont on Sunday May 24, 2015 @08:06AM
(#9596003)
Those two technologies serve two completely different needs. Would you claim C++ is dead because it doesn't have releases each year?
WPF is quite mature for what it does. The components underlying the web are changing rapidly. Comparing these two does not mean WPF is dead.
Re:Deep Dive into .NET Universal Windows App Development
by pjmlp on Sunday May 24, 2015 @07:32AM
(#9595949)
Only those that don't get that what matters is XAML.
Re:Deep Dive into .NET Universal Windows App Development
by tonyedgecombe on Sunday May 24, 2015 @11:20AM
(#9596486)
XAML is the least important part, it's the underlying object model where the value is.
In fact if they were starting from scratch now I doubt they would even use XML, it's not great a great way to edit large documents.
For example, here is a recent post on WPF work for VS 2015 [1]. It is very much alive and being used.
[1] http://blogs.msdn.com/b/dotnet/archive/2014/11/12/the-roadma...