When creating dlls (Add-ins) for a third party program that loads Native DLLs dynamically, is there a way, in a Mixed Mode DLL (C++/cli) to natively catch the fact that the .Net framework is not available. So that the Parent program that is dynamically trying to consume this DLL does not throw an error?
When creating dlls (Add-ins) for a third party program that loads Native DLLs dynamically,
Share
It might be possible to do something with a custom entry point in the dll, but I expect you are walking in ‘undocumented’ territory.
The only ‘simple’ way I can think to do this would be to create a native shim dll that performs the check and handles the condition in whatever way you see fit. If the framework is present it in turn loads the real plugin DLL and mirrors all calls through to it.
How easy this is will depend on the complexity of the plugin interface you are working with.