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 494193
To view parent comment, click here.
To read all comments associated with this story, please click here.
by moondevil on Tue 25th Oct 2011 07:00 UTC in reply to ".NET"
Member since:

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.

Reply Parent Score: 2

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

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

RE[3]: .NET
by Nelson on Tue 25th Oct 2011 07:36 in reply to "RE[2]: .NET"
Nelson Member since:

Here's how it works:

WinRT is basically every Windows API (input, devices, graphics, networking, etc.) implemented in native C++.

C#, VB.NET, and Javascript are consumers of the WinRT API.

WinRT exports metadata files which describe its API. Using this metadata, lightweight bridges are automatically generated for .NET languages and Javascript.

So I could write a WinRT component in C#, have the metadata autogenerated, and use it in C++ as if it was a native C++ class. Or use it in Javascript as a native javascript object.

The concept is incredibly powerful, but not exactly groundbreaking.

Basically: .NET, Javascript, and C++ are all first class citizens when it comes to WinRT. There is no favoritism like before, where .NET had to do convuluted interop into unmanaged code, and Javascript did god knows what.

Its all very slick, and did I mention fast?

Reply Parent Score: 2