Thanks for the pitch for my C++ Runtime blog post
|Coffeehouse||MS working on a same compiler for C++ AND C# ! Not in 'incubation' but for production !||78||Nov 14, 2013 at 6:34 PM|
Updated the MSDN code sample to be used with VS11 beta:
@guzeliya:I am not sure I understand the comment.
@yr_deng:Once again, this was a developer preview. There were some bugs and incomplete features related to debugging of C++/CX code. Those issues have now been fixed.
@yr_deng: That too seems like a bug in the developer preview. This has been fixed already in the internal builds and will be available in the next public release.
@yr deng:You should try the following:
- Clean the Imaging project.
- In the DemoCs project, add a reference to platform.winmd. Browse to "Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\platform.winmd" and add a reference
- Now add a reference to Imaging project.
- Try rebuild
This worked for me using your project.
Yes, the concept is similar. You can use the same C++ WinRT component in a C# app as well.
What you are observing is possibly a temporary bug in the Developer Preview. But if you can send me your app, I can certainly take a look.
sharma dot raman at microsoft
- The components you create using C++/CX as shown in this video are fully native components. There is no managed aspect to them.
- The fact that underlying technology is COM (not pInvoke btw) is irrelevant. The whole point is that the developer doesn't need to care about that. He can write regular C++ language and libraries constructs (with some new additions off course) and he gets language interop for free
Btw, the project that I used in this video can now be downloaded here: