Hi,
I'm trying to host CLR for advanced software protection
On .NET v2.0, this is possible
ICLRRuntimeHost *pCLR = NULL;
CorBindToRuntimeEx(..., &pCLR);
pCLR->SetHostControl(...)
ICLRControl *pCLRControl = NULL;
pCLR->GetCLRControl(&pCLRControl);
pCLRControl->SetAppDomainManagerType("MyDomainManager, version=1.0.0.0, culture=Neutral, PublicKeyToken=null");
pCLR->Start();
...
and then provide the assembly "MyDomainManager" under IHostAssemblyStore::ProvideAssembly
I don't want to have the scenario where the MyDomainManager.dll must be registered on the GAC or stored on the same folder
of the Loader.exe (CLR host), in other words, I want to have a "big software with many dll assemblies" converted on a standalone application
Thanks and best regards,
RB
Hosting under CLR v2.0
Jon Mc
If you'd like to file a bug on the MSDN Product Feedback Center, the hosting team can take a look at it and see if it would be possible to enable this scenario in the future.
-Shawn
Barrie
I would think that's possible -- have you tried it and found that you're not getting called to provide that assembly
-Shawn
MORRTI
Yes, I have tried but no success, only works if the assembly exists in disk.
The CLR call the my ProvideAssembly method, I return the correct assembly of "MyDomainManager" but:
pCLR->Start();
returns 0x80131522
// MessageId: COR_E_TYPELOAD
// Could not find or load a specific type (class, enum, etc).
Thanks
RB
AJN
Done thanks