"Getting Started with .NET Native" - https://msdn.microsoft.com/en-us/library/dn600165%28v=vs.110...
Also I doubt very much that we could have had Rosyln with VC 6.0 architecture, stuck in C++ and COM.
Microsoft was at the tipping point in 1999, then the dotNet thing happened and a lot of failures like dotNet based Shell/Explorer and WinFS for the failed Longhorn what turned into WinVista. Then the WinMobile 6.5 to 7 thing happened. The dotNet Framework seems to be legacy now - right? WinForms is legacy now. Silverlight is legacy. dotNet DirectX APIs are legacy. dotNetCore is the new thing, but in v1. UniversalApp based on C++ API seems to replace WinAPI - correct? Anyway WinAPI is still going strong, and almost all applications are WinAPI based.
Sometimes I would like to go back in time to 1998/99. But the good thing the WWW succeeded (and "The Microsoft Network" failed and original dotNet vision of software as a service got postponed by many years).
I have been doing greenfield WPF applications for companies in the life sciences industry in the last three years, and they will not move away from it any time soon.
Go back to native,Microsoft!