By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,994 Members | 1,567 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,994 IT Pros & Developers. It's quick & easy.

Howto avoid one common outdir in team builds?

P: n/a

I have a C# solution with 3 projects, a server-part, a client-part and
a common part.

When I build the solution in VisualStudio or using plain MSBuild on
the solution file, the outputs of the server-part goes into the server
projects output dir and the client-part into its output dir. This is
exactly what I want because I want to be able to identify which files
to deploy to the server and to the clients.

Now I try to setup a team build to build the solution on a build
server. The build works fine, but team build seems to enforce one
common output dir across all projects in the solution. This mixes the
client and the server files and it is no longer easy to identify
server files and client files.

The problem is that I cannot find any way to *not* have one common
output dir for the solution.

Does anyone have any ideas on how to solve this problem?

Thanks in advance!

Jun 8 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.