Windows 8 introduced a new kind of application to the world of Windows: The immersive application with a tablet-first design . Immersive applications will dominate Windows 8, existing applications will be relegated to a second-class status and accessible through a compatibility mode. When Microsoft first presented Windows 8, it gave the impression that immersive apps can only be written in HTML5. The article “Windows 8 for software developers: the Longhorn dream reborn?” on Ars examines whether that is true. This post summarizes the article.
The point of all this? It gives parity to native C++ and managed .NET code. Instead of being separate, each with its own different capabilities and strengths, they will be peers. If Microsoft adds new APIs to core Windows, the WinRT system will ensure that they're seamlessly available to managed code, meaning that .NET developers will no longer be at a disadvantage relative to native ones. Conversely, existing native applications can be updated to use the new UI without having to be substantially rewritten to use .NET. This same flexibility applies to Microsoft: putting native and .NET code on an equal footing opens the door to actually seeing .NET applications shipping with the operating system.
Microsofts silence. Quote:
It's understandable that Microsoft doesn't want to spill everything right now. Windows 8 is still a long way from completion, and plenty could change between now and BUILD. But developers aren't asking to hear everything now; they want to know a few salient details. Answering two questions would probably do the trick.The answer to both questions is likely yes. Additionally, one will be able to write first-class applications with many native features in HTML5. It is strange that Microsoft will wait until the BUILD conference in September 2011 to spread the good news.
- Will it be possible to write immersive applications using C++ or .NET?
- Will it be possible to write immersive applications using XAML?