To view parent comment, click here.
To read all comments associated with this story, please click here.
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?





Member since:
2005-07-08
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