Situation: We are a 12 person team who almost exclusively use Microsoft products. We have over 200 asp.net applications varying from WinForms, WebForms, and the many variants of web-services and windows services. Security is a closed network with Active Directory. Problem: Keeping services up to date, built correctly without conflicting settings or configs. Specific Issues: The services by default use the app.configThe app.config lacks connection strings, relying on machine.config2 WCF services might want different values for same connection stringThen 1 app.config adds a connection string, which is in source controlIgnore the changed app.config in source controlAnother user has update for the ignored app.config fileDiscard my changes, merge app.config and reapply my changesUpdating Installed services can be tedious, non-automated and overwrites app.config changes Proposal: Create Windows VMInstall the services on the VMUse my branch to build the serviceUse TFS to deploy to the VMPoint my service endpoints in my machine.config to my VMQuestion: Is this a reasonable solution to my problem or are there better tools to accomplish my goals? 
Creating a local Microsoft Stack virtual test environment for services and websites?
testing;web services;virtual machine;microsoft