|
#1
|
|||
|
|||
Best way to collect compiled dlls
We have a .net solution that has 60+ projects, it builds a setup project (.msi) in the end. The installer is then staged on a server for testing. It's a pretty simple build.
Now I need to also deliver all the compiled dlls separate from the installer. Any suggestions on how dlls can be collected from each project's output directory? I thought about parsing .sln to get project names and paths but it's hard to come up with a pattern in this file (there are web projects). We also have different build configurations, some in debug, some in release so sweeping the directories for .dlls didn't work too well either. We use VBP 5.7. Thanks. |
#2
|
|||
|
|||
Some options:
1) Configure your projects to compile all DLLs to a common directory. 2) Use the Copy Files action to copy the specified DLLs using advanced matching (v6 feature): http://www.visualbuild.com/Manual/filematching.htm 3) Parse the deployment project or project files for DLLs to copy. |
|
|