|
Solved it. It was a path issue. My interface DLL needed to go into the bin directory, while my resource DLL must be in the plug-in directory with my MLL file. The IEFrame.dll finding was a proverbial red herring. For those interested, I solved it by explicitly loading each of the first level library dependencies and when they all loaded ok I knew it was likely a path problem. Sure enough, moving the interface DLL to bin form plug-ins fixed it. Being new, it threw me off that my resource DLL must be in the plug-ins directory, but that is a side effect of how Windows handles satellite DLLS I suppose.
Author: daddyskates
| 
