From the instructions outlined in the sample README, it looks like to leverage this registration free mechanism, one needs to create the process - app - manifest and supply the WinRT activation class mapping in there.
But, how if I don't own the process, therefore unable to create or edit the app manifest?
Here's one scenario I'm faced with:
I have a C++ DLL that is loaded as a COM component by an external process that I don't own.
And from my C++ assembly, I would like reference a WinRT component written in C# and I can't figure out how to activate the runtime classes; is there any way to accomplish this?
I attempted to create a manifest for my C++ component - with a .dll.manifest extension - but that doesn't seem to work...
Can this be done with a reg-free free mechanism?
Thanks!
From the instructions outlined in the sample README, it looks like to leverage this registration free mechanism, one needs to create the process - app - manifest and supply the WinRT activation class mapping in there.
But, how if I don't own the process, therefore unable to create or edit the app manifest?
Here's one scenario I'm faced with:
I have a C++ DLL that is loaded as a COM component by an external process that I don't own.
And from my C++ assembly, I would like reference a WinRT component written in C# and I can't figure out how to activate the runtime classes; is there any way to accomplish this?
I attempted to create a manifest for my C++ component - with a
.dll.manifestextension - but that doesn't seem to work...Can this be done with a reg-free free mechanism?
Thanks!