quote:
Originally posted by RaceProUK
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?
Scripts support COM objects and not .NET(as far as i know) so the dll has to be COM Visible.
Scripting contest ends day after and i haven't been able to solve my dll's problem ;<. Help me!!!!
Edit : I just found out that MP!L when registers the dll doesn't add it to Global Assembly Cache resulting in failing of the dll
/ 
