Setting reference to non-distributable COM DLL

[notgumbel]

Good morning!

Long-time VBA programmer, mid-level ASP.NET programmer, doing my first in-depth VB.NET project. And I'm kind of stuck.

The project on which I'm working needs to reference a COM DLL that should already be on each user's machine in a set location (let's call it C:\toolkit\my.dll).

This DLL is not redistributable.

My project will be compiled into a DLL of its own, and then called by an VB.NET EXE that's being developed separately.

When I set a reference to C:\toolkit\my.dll in my Visual Studio project, the DLL is copied to the solution. Its "Copy Local" property is set to True.

This would then, if I'm not mistaken, include the C:\toolkit\my.dll file in any distributed solutions, correct?

What would be the best way to get around this? Is it as simple as setting my.dll's "publish status" as "prerequisite" in the EXE application?

Or could a wrapper be created for the DLL, referencing it as strictly C:\toolkit\my.dll?

Note: The DLL is copied as C:\Documents and Settings\HP_Owner\My Documents\Visual Studio 2005\Projects\TestBinding\TestBinding\obj\Debug\Interop.my.dll

Thanks much -- appreciate any guidance/pointers.

 

[dglienna]

If it was already installed and registered, I don't think you have to specify, as it's in system32, or in the app.path

Not positive though

-David
2006 & 2007 Microsoft Most Valuable Professional (MVP)
2006 Dell Certified System Professional (CSP)

 

[notgumbel]

I think my client is mainly worried about C:\Documents and Settings\HP_Owner\My Documents\Visual Studio 2005\Projects\TestBinding\TestBinding\obj\Debug\Interop.my.dll ... and whether that constitutes redistributing the original DLL (my.dll), which we're not supposed to be doing.