StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAutomated Builds in Team Foundation Server
text
Body
copied!<p>I am setting up an automated build for my solution. However, I get errors regarding failures in copying certain information to certain folders. This pertains to build events that each project in my solution has. </p> <p>What I was wondering is if there was a way to "turn off" the individual build events in the projects, or if there is a parameter to set somewhere that turns these build events off?</p> <p>The automated build I have set up already does what the individual project build events are supposed to do, and so it is trying to repeat itself and is causing problems. I still need the build events to be associated with the projects because when they're running outside of the development environment, they need to occur for the application to function properly (the build events have to do with dynamically updating information). </p> <p>Long story short, is there a way to turn off the builds that are associated with each individual project in my solution without actually deleting them? I need them to be there, I just need them to be "invisible" so-to-speak while I'm running the automated builds in the development environment.</p> <p>I apologize for the verbosity and for the vagueness of everything, it is difficult to explain things sometimes without giving away too much.</p> <p><em>EDIT: Not so much an edit as it is additional information for clarity, but nevertheless. The basic goal I am trying to accomplish is to disable the "post builds" that are associated with each of the projects in my solution. I want to keep them, just disable them while I'm running them through the in-house automated builds/tests</em></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload