Ask a question

Search Forums:

• Search Off-Topic Posts (Do Not Post Here) Forum
• Search All Using Forums Forums
• Search All Microsoft Forums

 

Non-assembly dependency management

• Wednesday, November 04, 2009 10:51 AMJan Svab

   
  

  0

  Sign In to Vote

  I'd like to know what is the preferred way of adding unmanaged DLLs into Visual Studio build chain. How can I add a reference to an unmanaged DLL, so that it gets copied to project target directory when building?
  Example: in my solution, I have a third party unmanaged library A.dll, which is wrapped into my managed wrapper B.dll. This is used by a library C.dll which is used by application D.exe. So in my solution I have three projects B, C, D and one file A.dll. How can I set up the build process so that A.dll gets copied to output folder of application D when D is built?
  
  In my current setup (probably not the "right" one) I have A.dll as a data file of project B, with "build action" set to "none" and "copy to output directory" set to "copy always". Then project reference to B is added to project C and project C is referenced in D. (Note that direct reference to B is not added to D, because D doesn't use classes in B, it uses just classes in C.)
  Unfortunately, this doesn't work. When building project B, the file A.dll is copied to output directory correctly. When building C, the B.dll and A.dll are also copied correctly to output directory of C. However, when building D, all the managed assemblies B.dll, C.dll and D.exe are in output directory, but the file A.dll is not copied. Seems that although the references themselves are propagating to more than one-level referencing, the files added to projects with "copy always" flag are non-propagating.
  
  Do I get something wrong? Or is there a better way how to set up the projects for this scenario?

  • Moved byRoahn LuoMSFTThursday, November 05, 2009 3:30 AMoff-topic issue. (From:Visual Studio Debugger)
  •  
  • Reply
  • Quote