Interop Question

[Altman]

I have just recently started playing around with VB.Net and I created a
small app that used an existing com dll written in VC++ 6.0. I then noticed
that it created a file called interop.mycom.dll. I also noticed that the
exe file would not run without this file. I did some searching and found
out that this is a wrapper to the com dll. I don't mind this except I have
a few questions on this. If I modify my com dll, does this mean I have to
rebuild my .Net app? Is there any way to tell .Net not use a wrapper? Is
there any loss in performance by .Net making this wrapper?

[Tom Shelton]

In article <OT**************@TK2MSFTNGP11.phx.gbl>, Altman wrote:

I have just recently started playing around with VB.Net and I created a
small app that used an existing com dll written in VC++ 6.0. I then noticed
that it created a file called interop.mycom.dll. I also noticed that the
exe file would not run without this file. I did some searching and found
out that this is a wrapper to the com dll. I don't mind this except I have
a few questions on this. If I modify my com dll, does this mean I have to
rebuild my .Net app? Is there any way to tell .Net not use a wrapper? Is
there any loss in performance by .Net making this wrapper?

The dll contains the RCW (runtime callable wrapper). This is necessary
if you want to use early binding in your project. You don't need it if
you want to use latebinding - but then you end up with another
performance hit on top of the one you already incured just from using
COM interop....

If you change modify your com object, then yes you'll need to generate a
new wrapper, and that would mean rebuilding your project.

--
Tom Shelton [MVP]