By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,389 Members | 2,070 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,389 IT Pros & Developers. It's quick & easy.

Interop reference files

P: n/a
I can't seem to figure out the difference between adding a COM dll
reference in VS2003 and by using TLBIMP.

I have a COM dll that references another COM dll, and I want the syntax
of my interop-filenames to be interop.<NameOfCOMDLL>.dll

I now make the first interop file

tlbimp COM1.dll /out:interop.COM1.dll /namespace:COM1

this gives me a interop file just as I expected and wanted.

Now I make the second file

tlbimp COM2.dll /out:interop.COM2.dll /namespace:COM2

This creates COM1.dll and interop.COM2.dll (with an assembly extern
pointing at COM1.dll, which means I can't use my interop.COM1.dll
anymore!!)

I have also tried:

tlbimp COM2.dll /r:interop.COM1.dll /out:in......

but that only generates the following error "Insufficient state to
deserialize the object. More information is needed"

If I instead Add a Ref to COM1 and COM2 in a VS project, both interop
files are created just as a wanted:
interop.COM1.dll
interop.COM2.dll (pointing at interop.COM1.dll)

can anybody tell me exactly what it is VS is doing that I'm not doing
using tlbimp?

Thank you

Morten la Cour

Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.