It has made things so much easier for us over the last ten years I'll never go without it, but we could if we had to. Otherwise we use TeamCity for everything else, including updating build agents with the contents of our 'vendor' repository which contains all of the versioned 3rd party libraries we reference in our projects. I can locally check for any breaking changes I may have missed before submitting them and deal with it up front.ДЄlso, it allows you to completely reproduce the build process locally allowing you to debug issues with it a lot easier than having to constantly submit changes to the server. You should always be able to build locally from a regular developer machine and I do it all the time because it's faster than submitting a personal build to the server and waiting for it to complete. The CMD sets a couple of options that prevent things like deploying anything or updating our release database (things that we don't already or don't want to automatically detect in the build script based on TC environment vars / properties set from the build config there). We have checked in a simple CMD file at the root of our repository that allows developers to build locally from the command line and specify which targets. We've been using TeamCity since 2007 and it's all NAnt scripts.

Youtrack teamcity integration