Tells to Visual Studio how to find the configuration option that needs transformation. Tells to Visual Studio that we want to replace original connection string. These attributes tell to Visual Studio 2010 packaging system how to modify Web.config so it works with current solution configuration. But there are two new attributes: Transform and Locator. īasically the connection string is like usual connection string in Web.config file. We wanted to use different connection string for product system where we use release configuration. This is default connection string that is used by all configurations that has no transform for this connection string. Let’s add new connection string to Web.Config file. Īs we can see there is only one transformation rule defined – remove debug attribute. Changing connection string for release configurationīy default, new transform for release configuration looks like this. You can find more information about transforms from Visual Web Developer Team Blogposting Web Deployment: Web.Config Transformation. Transform files contain only transforms – that is, modifications that one or another configuration needs in Web.config file to be made. Web.config file that was created by default contains all configuration options. Web.config transforms are not separate versions of main Web.config file. You can read in this point my blog entry Visual Studio 2010: Multiple web.config versions. Visual Studio 2010 will add transforms automatically. Just right click on Web.config file and select Add Config Transforms. By example you may want to add special configuration for test environment.Īdding config transforms is simple. If you want you can define more configurations. By default, solutions have two configurations: Debug and Release. Web.config versions are bound to solution configurations. I think there is no need to mention connectionStrings.
appSettings may include settings for paths that are different in different environments. These two blocks are the main sources of differences between development, test and production environments. web.config contains some section definitions and assembly, caching, pages, handlers and other configuration settings.īesides them we can add our own settings to appSettings block and connection strings to connectionStrings block. When we create web application project the web.config file is created automatically. Let’s see now how to play with web.config transformation so we can use one configuration on development environment and the other for production environment. Recently I wrote about Visual Studio 2010 and multiple web.config files support.
0 kommentar(er)
