Indirect assembly dependency issue
-
I have a native dll with some code that I want to leverage from managed C# applications. So I wrote a C++/CLI class library to implement an wrapper assembly. This works well but it creates a maintenance issue. In the C# client project, I added a reference to my wrapper assembly and whenever I build the client project, the assembly dll gets copied to the build target folder. However the dependent native dll does not get copied. So my question is, how do I include the native dll in the wrapper assembly dependency so that they are both copied when the client project is built.
-
I have a native dll with some code that I want to leverage from managed C# applications. So I wrote a C++/CLI class library to implement an wrapper assembly. This works well but it creates a maintenance issue. In the C# client project, I added a reference to my wrapper assembly and whenever I build the client project, the assembly dll gets copied to the build target folder. However the dependent native dll does not get copied. So my question is, how do I include the native dll in the wrapper assembly dependency so that they are both copied when the client project is built.
AFAIK, you don't. What you could do is have a post-build step which copies the files over.
Chill _Maxxx_
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
AFAIK, you don't. What you could do is have a post-build step which copies the files over.
Chill _Maxxx_
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierI'll second this. We have a post-build step copy the DLLs too. John