Automatically update reference to DLL in VS2008
-
I'm developing an application whose components are split between several VS solutions. For example: - Solution A includes projectA1 and projectA2 generating projectA1.dll and projectA2.dll - Solution B includes projectB1 generating projectB1.dll - Solution C includes a project which uses all the DLLs above to generate an application app.exe When I add the DLLs as references to solution C, they are copied in the output folder for app.exe. However, if I change something in Solution A, the modified DLL is obviously not automatically copied to Solution C. Is there a way to maintain this kind of structure avoiding manual copies? Regards, Andrea
-
I'm developing an application whose components are split between several VS solutions. For example: - Solution A includes projectA1 and projectA2 generating projectA1.dll and projectA2.dll - Solution B includes projectB1 generating projectB1.dll - Solution C includes a project which uses all the DLLs above to generate an application app.exe When I add the DLLs as references to solution C, they are copied in the output folder for app.exe. However, if I change something in Solution A, the modified DLL is obviously not automatically copied to Solution C. Is there a way to maintain this kind of structure avoiding manual copies? Regards, Andrea
One way of doing this would be to adapt your folder structure: instead of having three separate output folders (one for each project), create one folder that you set as output directory for all three projects. Another solution is to add the 'manual copy' as a post-build operation in the project settings: you simply add a "copy" operation at the end of the compilation.
Cédric Moonen Software developer
Charting control [v1.5] OpenGL game tutorial in C++ -
I'm developing an application whose components are split between several VS solutions. For example: - Solution A includes projectA1 and projectA2 generating projectA1.dll and projectA2.dll - Solution B includes projectB1 generating projectB1.dll - Solution C includes a project which uses all the DLLs above to generate an application app.exe When I add the DLLs as references to solution C, they are copied in the output folder for app.exe. However, if I change something in Solution A, the modified DLL is obviously not automatically copied to Solution C. Is there a way to maintain this kind of structure avoiding manual copies? Regards, Andrea
Metal76 wrote:
the modified DLL is obviously not automatically copied
Why should it? There is no dependency whatsoever from Solution A to Solution C. You have to change your output folders in Solution A appropriately or add a post-build step that makes the copy. Regards Thomas
www.thomas-weller.de Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software.