mixed mode assembly problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an assemble which is written in managed C++, this is a wrapper for
some native C++ code. I have created a setup project which installs the
assembly into a subdir of program files and it copies all the necessary dll's
there as well.

If I add a reference to this assembly in another standalone project it
copies the assemble dll locally but it does not copy all the other dlls and
so I can't run the app from within visual studio unless I copy the files by
hand. If I turn off 'copy local' on the reference it does not work either.

This is a small nuisance for myself but I need to hand the assembly
installer to other developers and have it 'just work' for them. Am I missing
something or is this a known issue?

thanks.

Gary.
 
=?Utf-8?B?R2FyeQ==?= said:
I have an assemble which is written in managed C++, this is a wrapper for
some native C++ code. I have created a setup project which installs the
assembly into a subdir of program files and it copies all the necessary dll's
there as well.

If I add a reference to this assembly in another standalone project it
copies the assemble dll locally but it does not copy all the other dlls and
so I can't run the app from within visual studio unless I copy the files by
hand. If I turn off 'copy local' on the reference it does not work either.

This is a small nuisance for myself but I need to hand the assembly
installer to other developers and have it 'just work' for them. Am I missing
something or is this a known issue?

thanks.

Gary.
Click to expand...

Hi Gary
The "copy local" option copies managed assemblies. You can either
automatically copy the other files using a pre-build action, or you
can put the original DLL directory in the PATH environment variable
and then the Windows loader will be able to find them.

Alon Fliess
CTO
The Sela Group
 
Back
Top