An Assembly Needs 2 Copies Of A VB6 Com Dll To Work With.

Hey guys,

I'm using CLR integration on SQL Server 2005 to call functions from a COM dll made with VB6. I do this to keep some important parts in packed unmanaged code, to make reverse engineering harder.

I keep the COM dll in the system directory. When it's referenced from a .net project, VS copies and uses it as 'interop.myCOM.dll'. When I add the assembly to SQL Server, it needs the referenced 'interop.myCOM.dll' file added. When a class from the COM dll is called by a CLR stored procedure, it needs to locate the real COM dll.

So, the same dll has to be in two different places in two different forms, one as an assembly (interop), and one in its own place. I guess the 'interop' one is not really used, but it just helps to retrieve class information during design time and initialization or something. Everything works ok, but thinking about the packing step and others, this makes things messy. How can I prevent using two copies of my COM dll?


I load the COM class as follows:





Code Snippet

Private Shared ReadOnly m_myClass As myCOM.clsGeneric = New myCOM.clsGeneric

then map stored procedures (shared functions) to related functions of the m_myClass object.