Linked by twitterfire on Mon 24th Oct 2011 22:52 UTC
General Development "Looking past the Metro hype, the Build conference also revealed promising road maps for C#, Visual Studio, and the .Net platform as a whole. Perhaps the most exciting demo of the conference for .Net developers, however, was Project Roslyn, a new technology that Microsoft made available yesterday as a Community Technology Preview. Roslyn aims to bring powerful new features to C#, Visual Basic, and Visual Studio, but it's really much more than that. If it succeeds, it will reinvent how we view compilers and compiled languages altogether."
Thread beginning with comment 494148
To read all comments associated with this story, please click here.
.NET
by WorknMan on Tue 25th Oct 2011 01:03 UTC
WorknMan
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?

Reply Score: 2

RE: .NET
by tomcat on Tue 25th Oct 2011 01:57 in reply to ".NET"
tomcat Member since:
2006-01-06

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.

Reply Parent Score: 2

RE[2]: .NET
by Nelson on Tue 25th Oct 2011 03:12 in reply to "RE: .NET"
Nelson Member since:
2005-11-29

They're not mutually exclusive, they both co-exist.

WinRT projects itself across the managed boundary. In fact, you can write WinRT components in .NET.

Reply Parent Score: 2

RE[2]: .NET
by kaiwai on Tue 25th Oct 2011 03:34 in reply to "RE: .NET"
kaiwai Member since:
2005-07-06

"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.

Reply Parent Score: 2

RE: .NET
by moondevil on Tue 25th Oct 2011 07:00 in reply to ".NET"
moondevil Member since:
2005-07-08

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

Reply Parent Score: 2

RE[2]: .NET
by WorknMan on Tue 25th Oct 2011 07:25 in reply to "RE: .NET"
WorknMan Member since:
2005-11-13

They complement each other. WinRT is replacing Win32 not .Net.


Why do we need both of these? Or in other words, when would you use one instead of the other?

Reply Parent Score: 2