"Debi" <debi@nospam.com> schrieb:
> I'm referencing a vb dll from my .net windows application. When I deploy
> this application to the client's machine should I include this dll, or is
> the
> interop dll that vb creates enough? If I have to include the vb dll, do I
> have to register the dll using regsvr32?
Deployment in Visual Studio -- Deployment and Dependencies
<URL:http://msdn2.microsoft.com/en-us/library/12w3fhd2(VS.80).aspx>
Note that the VB6 runtime libraries must to be installed in order to use the
VB6 DLL on the target machine.

Signature
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>
Debi - 28 Apr 2006 21:15 GMT
Thanks for the reply. I'm familiar with deployment as discussed in the url,
but not sure on how the interop works. Suppose my .net application is calling
a vb dll, is it enough that it's present in the application directory or
should I register it. The article says it will look in GAC and then app.
folder. But when I install my app without registering the assembly it gives
an error.
One more question is: Suppose I use regasm to register the dll, instead of
regsvr32 will that make any difference?
> "Debi" <debi@nospam.com> schrieb:
> > I'm referencing a vb dll from my .net windows application. When I deploy
[quoted text clipped - 8 lines]
> Note that the VB6 runtime libraries must to be installed in order to use the
> VB6 DLL on the target machine.