On 15 mai, 08:48, Kenneth Porter <shiva.blackl...@sewingwitch.com>
wrote:
> Are there any HOWTOs that show how to do this?
>
> My client is using C# in VS 2008 and my unmanaged DLL and managed C++/CLI
> wrapper are in VS 2005. What do I need to do to make sure the necessary C++
> runtime is provided along with the DLL and wrapper?
>
> Do I just give him the two DLLs to copy into his app's directory and a copy
> of the 2005 redistributable runtime installer?

Use Dependency Waker (depends.exe) to check wether your native DLL (or
the mixed mode wrapper) is relying on some DLLs that are not part of
the OS.

You should also check wether the native DLL is relying on another
component that it loads dynamically (eg, a DLL lodade by LoadLibrary,
a COM component or Active X...).

At the end of the day, it's up to you to know what your code is doing,
and what it is relying on...

Arnaud

(E-Mail Removed) wrote in news:c564737c-378b-499f-8db0-
(E-Mail Removed):

> You should also check wether the native DLL is relying on another
> component that it loads dynamically (eg, a DLL lodade by LoadLibrary,
> a COM component or Active X...).
>
> At the end of the day, it's up to you to know what your code is doing,
> and what it is relying on...

I know *what* to package. I just don't know the best practices for doing
so.

For now, I'm providing the 2 DLLs and the installer for the redistributable
runtime.

On 16 mai, 22:13, Kenneth Porter <shiva.blackl...@sewingwitch.com>
wrote:
> adeba...@club-internet.fr wrote in news:c564737c-378b-499f-8db0-
> 39dc7dfc3...@m36g2000hse.googlegroups.com:
>
> > You should also check wether the native DLL is relying on another
> > component that it loads dynamically (eg, a DLL lodade by LoadLibrary,
> > a COM component or Active X...).
>
> > At the end of the day, it's up to you to know what your code is doing,
> > and what it is relying on...
>
> I know *what* to package. I just don't know the best practices for doing
> so.

There are several options. For Native applications (or partly native
applications), a .MSI is the best "Micrososft" bet (there are non-
Microsoft alternatives such as InnoSetup).
You can create a MSI with a "Setup" project in Visual Studio.

> For now, I'm providing the 2 DLLs and the installer for the redistributable
> runtime.