quote:
Originally posted by -!Felu!-
-The dll is COM Visible
-The dll is registered with ResAsm utility and is also placed in <DotNetFiles> in the ScriptInfo.xml
Why do I get the feeling it's this that's causing issues? Granted, I'm not familiar with all the Scripting API, but surely trying to load the DLL as a COM object when it's also exposed as a .NET assembly may be causing problems?