Menu
After the WinRT presentation, I'm confused about the role of the .net framework in the Microsoft development stack.
Is it necessary for developing WinRT applications?
730
C#/WinRT is a NuGet-packaged toolkit that provides Windows Runtime (WinRT) projection support for the C# language. A projection assembly is an interop assembly, which enables programming WinRT APIs in a natural and familiar way for the target language.
NET Standard is supported on UWP.
WinRT can be described as an API at the same level as Win32. The only difference with Win32 is that WinRT is exposed to all application developers.
UWP does NOT run on the . NET Core App runtime like a . NET Console does, if that makes sense.
As I understand it you can build a WinRT app in 3 ways
The WinRT "object" are ref counted like COM was, however they have good meta data so .net can make them look like .net objects. (likewise jscript can make them look like jscipt objects)
So .net is not necessary to develop WinRT applications if you wish to use jscript or C++.
148
If you are developing a Windows 8 Metro style application, then you will be using WinRT whether you choose to use HTML5/JS, Xaml or C++. Note that C#/VB.NET and Xaml in Metro apps only expose a subset of the .NET Framework. WinRT provides a sort of sandboxed environment for the apps.
If you are developing "classic" Desktop Applications, then you'll likely use the .NET Framework and its full awesomeness.
They really are two different platforms for building two different kind of apps. WinRT for fully imersive apps that can utilize touch and other sensors. And .NET for any other application you want to build. Remember that you can still utilize touch (and most likely the other sensor API's as well) within any .NET application.
29
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
