In WinRT is C++ really C++ or just some phony thing that looks like C++?

Translate This Page

In WinRT is C++ really C++ or just some phony thing that looks like C++?

Rate This
  • Comments 2

Let’s face it, C++ is getting a little boring as is.  But to deviate from the C++ spec is evil.  What to do?  Well if the language compiles like C++ specified language is that enough? Here is the explanation from the Dev Center site:

Visual C++ in Visual Studio 11 for Windows 8 Consumer Preview has a revolutionary new native C++ programming model for creating Metro style apps and components. In the new model, native C++ can interop directly with JavaScript and managed code without the need for intermediate software layers.

What does this mean to me? (Or you.)  Well I better get back up to speed with using C++, C++ in Visual Studio 11 appears to have taken on a new attitude: I need a presentation layer solution or lose traction to the real world.

In only a few steps you can create your first C++ app that connects to the XAML presentation layer.  Likely if you work at it a little you could use HTML5.


Or you could see my blog for tomorrow for a super simple Hello World using the XAML/C++: (after 3/18/2012)



This is great stuff, being able to use C++ with a real interface.  Not that I think it is efficient, or cost effective for most applications, there are still a great number of development houses that are efficient at building C++ apps.

Leave a Comment
  • Please add 6 and 2 and type the answer here:
  • Post
  • I've never figured out which is more efficient C++ or C#.  

  • Hi Cron22!

    C# is much more efficient from the production, maintenance and support point of view.  C++ is more efficient from the point of view of creating drivers, portability, and lower level work efforts.

    But with XAML with C++, there are some interesting improvements on production.  Support and maintenance for C++ will always be higher.

Page 1 of 1 (2 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control


  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them