Writing a WinRT component using WRL

Question

I have been using the project template called "Windows Runtime Component" that ships with VS2012 in order to create a C++/CX based WinRT component.

I now wish to do the same thing without using C++/CX but through WRL. When I do this, there are some things (referencing, automatic packaging with the main app project, Winmd-based intellisense etc.) that don't work in VS2012. How can I make sure that I can use WRL in my component project and still get the full IDE experience like I get with C++/CX based template?

What would be the purpose of avoiding C++/CX for such scenario? — Filip Skakun
People have their reasons. The idea is that there is a choice. — Raman Sharma
I'm not questioning it as being something not worth doing. I am simply curious why would people have such a reason. You don't have to say if you can't. — Filip Skakun
The idea is not to avoid C++/CX but just in case someone has a preference for WRL. One reason I have heard people say is to not use non-standard language extensions. Another reason is to avoid exceptions in their internal code. — Raman Sharma
But WRL isn't a standard library is it? So if you used it you would be using non-standard library anyway. C++/CX should only be used for that WinRT Component interface layer anyway, so an actual library would remain the same, no? — Filip Skakun

Raman Sharma Raman Sharma · Accepted Answer · 2012-12-24T01:39:53

Take a look at the Visual Studio project template for WRL components here: http://visualstudiogallery.msdn.microsoft.com/346e6fbc-6508-43c8-af7f-9a922bb57128

This achieves a similar result both at design-time and at runtime as does the C++/CX based project template.

Writing a WinRT component using WRL

1 Answers