COM / .NET interop

COM / .NET interop

Post by Stijn Lamber » Wed, 28 May 2003 22:36:21

Hello all,

Is it in any way possible to call a .NET-assembly from VB6-COM when:

* It's not residing in the calling-application's Path
* I don't want to register it in the machines GAC (Global assembly cache)

I already exported te TypeLib-info using Regasm.exe /tlb, but the
COM-application can't find the .NET assembly because it's in another

Is there any way to let the COM-object know where to search for the
.NET-assembly outside of it's own path and outside of the GAC ?


Stijn Lambert
Real Software Group
Industry Division
Prins Boudewijnlaan 26       B-2550 KONTICH

Real Software e-mails kunnen vertrouwelijke informatie bevatten . Zij mogen
niet meegedeeld worden aan derden zonder voorafgaandelijke schriftelijke
dit e-mailadres heeft een professioneel karakter en kan door Real Software
gecontroleerd en/of gelezen worden binnen de wettelijk toegelaten grenzen.


1. URGENT HELP - COM/.Net Interop Issue

Going live and hit a snag...!

We have a    [vbdotnet.exe]   referencing a    [vb6COM.dll]   referencing a
( this is because we have proprietary code in the vb6COM.dll and too easy to
see if in .net code...)

Built an installation package in which ALL dlls'  Register  property is set
to:  vsdraCOMRelativePath

Referencing etc all works fine in the DEV environment BUT the COM.dll throws
multiple errors, for example:
"ActiveX component could not create object" once installed on the Test

My assumption is that this is all to do with referencing/registration of
each component.
Each time the   [vbdotnet.dll]   is rebuilt, it needs to be re-referenced in
the [vb6COM.dll] and THAT then needs recompiling (maintaining compatibility,
same GUID etc)

Is there something else that needs to be set/configured on the
target/install machine to enable this COM/.Net interop to work?
Should the COM.dll be packaged seperately...??


Thanks, LM

2. Windows 98 Version 4-10-1998 & Version 4-10-222A(Second Edition) discrepancy

3. COM / .NET interop: duplicate base interfaces methods in derived interfaces.

4. ODBC Link from PV via TRN to secondary AS/400

5. COM /.NET interop

6. Netware Lite?

7. Java COM Interop / J++ COM Interop


9. Failure when passing COM object through InterOp to .NET COM object

10. How to get custom error message in COM interop (COM calling .NET)?

11. .Net to COM and back to .Net interop

12. Does .NET uses the RCW when using .NET componet with COM Interop enabled?

13. .Net Remoting and COM Interop question