3 ms·

Many of these technologies are certainly supported (WinForms, WPF, Silverlight, etc). It's just that there isn't and won't be any new development on these produ

Many of these technologies are certainly supported (WinForms, WPF, Silverlight, etc). It's just that there isn't and won't be any new development on these products in the future. Microsoft is putting all of their focus into WinRT and Web development. On the one hand, yeah it kind of sucks that the platforms they built over the last 10-12 years are obsolete. On the other hand, they're moving an incredible pace around developing tools for WinRT and Web development (especially Web, which I keep up with in my day job).

Pxtl 13y ago
MS went through a terrible process of whipping up and discarding frameworks a few years back... the churn of Linq2SQL being abandoned almost as soon as it was launched, Silverlight, all those rapid-fire dead-ends. Plus there were some horrible false-starts - EF3.5 was nightmarish, as was ClickOnce, and I've been less-than-impressed with SqlCE. I love the newish linguistic features of C#, but I've seriously slacked off in learning the new libs after being burned so many times. I still use WinForms for Pete's sake. Has it settled down enough? Is it safe to start learning about WinRT? To actually figure out how MVC actually works instead of doing my best to ignore it while I do everything in Javascript and the Controllers?
- daigoba66 13y ago
  All of the web stuff (ASP.NET MVC, etc) has the advantage of being open source (real open source, Apache 2 licensed, and accepts contributions). The team is also very open with the community and releases frequently. They're also working with with the OWIN (http://owin.org/ http://owin.org/) standards so that these projects don't have to be tied to Windows/IIS. It all moves very fast however, which might not necessarily be a good thing for LOB developers. I can't really speak for WinRT. I've never touched or looked at the developer tools. And I've not ever really used an app as a user. The only reason I think it's here to stay, for a little bit anyway, is that it's the _only_ way to develop software that runs on Windows Phone or Windows RT tablets (other than Web apps).

Pxtl 13y ago

MS went through a terrible process of whipping up and discarding frameworks a few years back... the churn of Linq2SQL being abandoned almost as soon as it was launched, Silverlight, all those rapid-fire dead-ends. Plus there were some horrible false-starts - EF3.5 was nightmarish, as was ClickOnce, and I've been less-than-impressed with SqlCE. I love the newish linguistic features of C#, but I've seriously slacked off in learning the new libs after being burned so many times. I still use WinForms for Pete's sake. Has it settled down enough? Is it safe to start learning about WinRT? To actually figure out how MVC actually works instead of doing my best to ignore it while I do everything in Javascript and the Controllers?

daigoba66 13y ago
All of the web stuff (ASP.NET MVC, etc) has the advantage of being open source (real open source, Apache 2 licensed, and accepts contributions). The team is also very open with the community and releases frequently. They're also working with with the OWIN (http://owin.org/ http://owin.org/) standards so that these projects don't have to be tied to Windows/IIS. It all moves very fast however, which might not necessarily be a good thing for LOB developers. I can't really speak for WinRT. I've never touched or looked at the developer tools. And I've not ever really used an app as a user. The only reason I think it's here to stay, for a little bit anyway, is that it's the _only_ way to develop software that runs on Windows Phone or Windows RT tablets (other than Web apps).