Ok I get your point... We're using direct calls to devenv.exe instead of compiling everything ourselves... This leads to a couple of issues (one is scalability!) but for us it was finally the best option.
In your situation would it be acceptable to have two separate targets in one build script ? If the script gets too big you could factor out the common part and include it with the include task (what I have done on other scripts of this kind).
> Although your right, whats the point of a debug build on your build server?
The idea behind that was when we face an issue, we are able to quickly replace the assemblies to debug them (the source code was also published on the build server aside the debug build). But finally we tend to never use this feature, so we're dropping it out.
Thibaut
