should vb dll be packaged for interop -- dotnet interop

Debi
4/28/2006 1:15:02 PM

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?

[quoted text, click to view]

Herfried K. Wagner [MVP]
4/28/2006 2:22:04 PM

"Debi" <debi@nospam.com> schrieb:
[quoted text, click to view]

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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet interop

dotnet interop : should vb dll be packaged for interop