ASP.NET 4 Unleashed

Using Web.config Transformations

So far we’ve seen that with Visual Studio 2010 we can create new web deployment packages that drastically simplify the deployment of applications to interim environments such as QA and Staging, but what about the configuration? Application settings, connection strings, web service endpoints, and hundreds of other pieces of configuration all typically vary depending on whether the application is running on a developer workstation, in QA, in Staging, or in Production. So how do we take advantage of the great web deployment tools but still have varying configuration files?

Before Visual Studio 2010, we would write custom build scripts that would replace our Web.config files with custom files specific to certain ...