471,339 Members | 1,258 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,339 software developers and data experts.

Interop reference files

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
0 2622

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by roy | last post: by
reply views Thread by roy | last post: by
reply views Thread by keefah | last post: by
8 posts views Thread by Rob Edwards | last post: by
reply views Thread by lacour | last post: by
5 posts views Thread by Yoavo | last post: by
reply views Thread by Tina | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.