I am using the plugin architecture in Windows Azure. To survive the reboot, I want to store the plug-in DLL modules in the blob, and not in the file system. However, I am having problems with dependencies between DLLs. I have the following situation:
- DLL A depends on DLL B
- Both are saved in Azure Blob
- I load DLL B first, no problem.
- Then I try to load DLL A - Exception so that it cannot find the file containing DLL B
This, of course, is very logical since DLL B is not located on the local file system. Is there a way to force the class loader to not try to load DLL B, but rather look into the memory since it is already loaded? Or do I need to go back and review the design ....
BR Jonas
source share