title: What are the pros and cons of writing C#/XAML vs. C++/XAML WinRT applications in Windows8?
body: <p>I'd like to go down the route of porting a WPF/Silverlight component to Windows 8. For a bit of context, the component is a <a href="http://www.scichart.com" rel="noreferrer">real-time WPF Chart</a>, which uses a mixture of WPF/XAML and bitmap rendering to achieve high performance. </p>
  
  <p>I'd like the component to be Metro compatible, e.g. used in metro mode as well as desktop mode. I read a lot about creating <a href="http://www.codeproject.com/Articles/262151/Visual-Cplusplus-and-WinRT-Metro-Some-fundamentals" rel="noreferrer">C++/WinRT</a> applications in Windows 8 as well as <a href="http://msdn.microsoft.com/en-us/library/windows/apps/xaml/br229571.aspx" rel="noreferrer">C#/XAML</a> applications, but what are the differences between the two frameworks? </p>
  
  <p>Are there limitations if you choose C#/XAML over C++/XAML? Also consider the porting from C#/Xaml in .NET4.0 to Windows8 would be far easier if I could stick to C#/XAML, however will I be able to create a fully featured Metro component using this method? </p>
  
  <p>Your comments/suggestions appreciated. </p>
  
  <p><strong>Edit:</strong> </p>
  
  <p>If you're voting to close this thread, please post a comment why. Its a valid question, has +6 votes, four answers and one favourite. Seems reasonable to keep it to me!</p>