Linked by twitterfire on Mon 24th Oct 2011 22:52 UTC
Thread beginning with comment 494148
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
"So what's the deal... is MS leaving .NET behind, or are they not? I thought WinRT was supposed to be the new 'Jesus API' to rule them all?
I'm sure that .NET will be around for a long time for server development. But WinRT is the new Windows client API. "
But from what I observe it is for metro-only applications - 30 years on and Microsoft still haven't come up with the horrific mess that is common controls and dialogues.
So what's the deal... is MS leaving .NET behind, or are they not? I thought WinRT was supposed to be the new 'Jesus API' to rule them all?
They complement each other. WinRT is replacing Win32 not .Net.
.Net developers can also directly make access of WinRT APIs. It is still C#, VB.Net, F# and so on.
One of the good things of WinRT is that Hungarian notation is finally dead. Even Microsoft coding guidelines now advice against it, by calling a relic.
http://1code.codeplex.com/releases/view/53729#DownloadId=156490





Member since:
2005-11-13
So what's the deal... is MS leaving .NET behind, or are they not? I thought WinRT was supposed to be the new 'Jesus API' to rule them all?