Our build server has been using the following properties for some time
OutputPath=c:\output;
OutputDir=c:\output;
OutDir=c:\output;
ReferencePath=c:\output;
AdditionalLibPaths=c:\output
Which make all output go to a common folder, and also allow resolving references for that same folder. This works great because
- it's an optimization over building locally and copying references locally
- I need all my dll's in a common folder anyways so I can zip and ship
Since this is working great on the build box, I would like to bring the same experience to our developers. I want our IDE builds to behave the same way.
In other words, I want the work flows our developers always use (build solution, build project) to behave just like I described happens on the build box.
I could easily accomplish this if I asked the team to create an VS.Net external tool to a batch file that just calls msbuild on the selected project with the desired properties. But ideally they wouldn't have to change their workflow.
I want to know
- if anybody else is doing this?
- what is the best way to do it?
- do I need to edit every single csproj file or use an external tool or batch file
Thanks