Your official information source from the .NET Web Development and Tools group at Microsoft.
We have earlier discussed about Web Deployment and Web Packaging quite a bit, today I wanted to dive into web.config transformation. If you would like to check out the other topics please read through the earlier blog posts below:
Usually web applications go through a chain of server deployments before being finally being deployed to production environment. Some of these environments can be Developer box (Debug), QA Server, Staging/Pre-Production, Production (Release). While transitioning between these environments various settings of the web application residing in web.config file change, some of these settings can be items like application settings, connection strings, debug flags, web services end points etc.
VS10’s new web.config transformation model allows you to modify your web.config file in an automated fashion during deployment of your applications to various server environments. To help command line based deployments, Web.Config transformation is implemented as an MSBuild task behind the scene hence you can simply call it even outside of deployment realm.
I will try to go through below steps to explain web.config transformation in detail
Step 1: Creating a “Staging” Configuration on your developer box
Debug and Release build configurations are available by default within Visual Studio but if you would like to add more build configurations (for various server environments like “Dev”, “QA”, “Staging”, “Production” etc then you can do so by going to the Project menu Build --> Configuration Manager… Learn more about creating build configurations.
Step 2: Adding a “Staging” Web.Config Transform file to your project
One of the goals while designing web.config transformation was to make sure that the original runtime web.config file does not need to be modified to ensure that there would be no performance impacts and also to make sure that the design time syntax is not mixed with runtime syntax. To support this goal the concept of Configuration specific web.config files was introduced.
These web.config files follow a naming convention of web.configuration.config. For example the web.config files for various Visual Studio + Custom configurations will look as below:
Any new Web Application Project (WAP) created in VS10 will by default have Web.Debug.config and Web.Release.config files added to the project. If you add new configurations (e.g. “Staging”) or if you upgrade pre-VS10 projects to VS10 then you will have to issue a command to VS to generate the Configuration specific Transform files as needed.
To add configuration specific transform file (e.g. Web.Staging.Config) you can right click the original web.config file and click the context menu command “Add Config Transforms” as shown below:
On clicking the “Add Config Transform” command VS10 will detect the configurations that do not have a transform associated with them and will automatically create the missing transform files. It will not overwrite an existing transform file. If you do not want a particular configuration transform file then you can feel free to delete it off.
Note: In case of VB Web Application Projects the web.configuration.config transform files will not be visible till you enable the hidden file views as shown below:
The transform files are design time files only and will not be deployed or packaged by VS10. If you are going to xCopy deploy your web application it is advised that you should explicitly leave out these files from deployment just like you do with project (.csproj/.vbproj) or user (.user) files…
Note: These transform files should not be harmful even if deployed as runtime does not use them in any fashion and additionally ASP.NET makes sure that .config files are not browsable in any way.
Step 3: Writing simple transforms to change developer box connection string settings into “Staging” environment settings
Web.Config Transformation Engine is a simple XML Transformation Engine which takes a source file (your project’s original web.config file) and a transform file (e.g. web.staging.config) and produces an output file (web.config ready for staging environment).
The Transform file (e.g. web.staging.config ) needs to have XML Document Transform namespace registered at the root node as shown below:
<?xml version="1.0"?> <configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"> </configuration>
Note: The transform web.config file needs to be a well formed XML.
Inside the XML-Document-Transform namespace two new attributes are defined. These attributes are important to understand as they drive the XML Transformation Engine.
Transform – This attribute inside the Web.Staging.config informs the Transformation engine the way to modify web.config file for specific configuration (i.e. staging). Some examples of what Transforms can do are:
Locator – This attribute inside the web.staging.config helps the Transformation engine to exactly pin-point the web.config node that the transform from web.staging.config should be applied to. Some examples of what Locators can do are:
Based on the above basic understanding let us try to transform connection string from original web.config file to match Staging environment’s connection string
Let us examine the original web.config file and identify the items to replace... Let’s assume that the original Web Config file’s connection string section looks as below:
<?xml version="1.0" encoding="UTF-8"?> <configuration> <connectionStrings> <add name="personalDB" connectionString="Server=DevBox; Database=personal; User Id=admin; password=P@ssw0rd" providerName="System.Data.SqlClient" /> <add name="professionalDB" connectionString="Server=DevBox; Database=professional; User Id=admin; password=P@ssw0rd" providerName="System.Data.SqlClient" /> </connectionStrings> .... .... </configuration>
NOTE: It is not advisable to keep connection string unencrypted in the web.config file, my example is just for demonstration purposes.
Let us assume that we would like to make following changes to web.config file when moving to staging environment
To make the above change happen we will have to open web.Staging.Config file and write the below piece of code
<?xml version="1.0"?> <configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"> <connectionStrings> <add name="personalDB" connectionString="Server=StagingBox; Database=personal; User Id=admin; password=StagingPersonalPassword" providerName="System.Data.SqlClient" xdt:Transform="Replace" xdt:Locator="Match(name)" /> <add name="professionalDB" connectionString="Server=StagingBox; Database=professional; User Id=professional; password=StagingProfessionalPassword" providerName="System.Data.SqlClient" xdt:Transform="Replace" xdt:Locator="Match(name)"/> </connectionStrings> </configuration>
The above syntax in web.staging.config has Transform and Locator attributes from the xdt namespace. If we analyze the connection string node syntax we can notice that the Transform used here is “Replace” which is instructing the Transformation Engine to Replace the entire node
Further if we notice the Locator used here is “Match” which is informing Transformation engine that among all the “configuration/connectionStrings/add” nodes that are found, pick up the node whose name attribute matches with the name attribute of <add> node in web.Staging.config.
Also if you notice web.Staging.config does not contain anything else but the connectionStrings section (i.e. it does not have <system.web> and various other sections that web.config file usually has, this is because of the fact that the Transformation Engine does not require a complete web.config file in web.staging.config. It does the merging for you thus saving you duplication of all the rest of the sections in web.config file.
Simplest Approach: If you do not mind replicating the entire web.config file in web.staging.config then you can certainly do so by copying the entire web.config content into web.staging.config and change the relevant nodes inside web.staging.config. In such a situation you will just have to put xdt:Transform="Replace" attribute on the topmost node (i.e. configuration) of web.staging.config. You will not need xdt:Locator attribute at all as you are replacing your entire web.config file with web.staging.config without Matching anything.
So far we have seen one Transform (i.e. Replace) and one Locator (i.e. Match), we will see various other Transforms and Locators further in the post but first let us understand how we can produce the Transformed web.config file for the Staging environment after using original web.config and web.staging.config.
Step 4: Generating a new transformed web.config file for “Staging” environment from command line
Open Visual Studio Command prompt by going to Start --> Program Files –> Visual Studio v10.0 –> Visual Studio tools –> Visual Studio 10.0 Command Prompt
Type “MSBuild “Path to Application project file (.csproj/.vbproj) ” /t:TransformWebConfig /p:Configuration=Staging" and hit enter as shown below:
Once the transformation is successful the web.config for the “Staging” configuration will be stored under obj -->Staging folder under your project root (In solution explorer you can access this folder by first un-hiding the hidden files) :
You can now verify that the new staging web.config file generated has the changed connection string section.
Step 5: Generating a new transformed web.config file for “Staging” environment from VS UI
Right Click on your project and click Package –> Create Package
The Create Package step already does web.config transformation as one of its intermediate steps before creating a package and hence you should be able to find the transformed web.config file in the same place as described in Step 4
Step 6: Understanding various available web.config Transforms and Locators
The inbuilt xdt:Locators are discussed below.
<connectionStrings> <add name="Northwind" connectionString="connectionString goes here" providerName="System.Data.SqlClient" xdt:Transform="Replace" xdt:Locator="Match(name)" /> </connectionStrings>
· Condition - Condition Locator will create an XPath predicate which will be appended to current element’s XPath. The resultant XPath generated in the below example is “/configuration/connectionStrings/add[@name='Northwind or @providerName=’ System.Data.SqlClient’ ]”
This XPath is then used to search for the correct node in the source web.config file
<connectionStrings> <add name="Northwind" connectionString="connectionString goes here" providerName="System.Data.SqlClient" xdt:Transform="Replace" xdt:Locator="Condition(@name=’Northwind or @providerName=’System.Data.SqlClient’)" /> </connectionStrings>
· XPath- This Locator will support complicated XPath expressions to identify the source web.config nodes. In the syntax example we can see that the XPath provided will allow user to replace system.web section no matter where it is located inside the web.config (i.e. all the system.web sections under any location tag will be removed.)
<location path="c:\MySite\Admin" > <system.web xdt:Transform="RemoveAll" xdt:Locator="XPath(//system.web)"> ... </system.web> </location>
· Remove - Removes the first matching element along with all of its children <assemblies xdt:Transform="Remove"></assemblies>
· RemoveAll - Removes all the matching elements from the destination’s web.config (e.g. staging environment’s web.config file).
<connectionStrings> <add xdt:Transform="RemoveAll"/> </connectionStrings>
· Insert - Inserts the element defined in web.staging.config at the bottom of the list of all the siblings in the destination web.config (e.g. staging environment’s web.config file).
<authorization> <deny users="*" xdt:Transform="Insert"/> </authorization>
· SetAttributes - Takes the value of the specified attributes from the web.staging.config and sets the attributes of the matching element in the destination web.config. This Transform takes a comma separated list of attributes which need to be set. If no attributes are given to SetAttributes transform then it assumes that you would like to Set all the attributes present on the corresponding node in web.staging.config <compilation batch="false"xdt:Transform="SetAttributes(batch)">
· RemoveAttributes - Removes the specified attributes from the destination web.config (i.e. staging environment’s web.config file). The syntax example shows how multiple attributes can be removed.
<compilation xdt:Transform="RemoveAttributes(debug,batch)"> </compilation>
<authorization> <deny users="Vishal" xdt:Transform="InsertAfter(/configuration/system.web/authorization/allow[@roles='Admins'])” />
<authorization> <allow roles=" Admins" xdt:Transform="InsertBefore(/configuration/system.web/authorization/ deny[@users='*'])" /> </authorization>
Some advanced points to note:
<location path="c:\MySite\Admin" xdt:Locator="Match(path)">> <system.web> ... Bunch of transforms written under here will .... only apply if location path = C:\MySite\Admin </system.web> </location>
Step 7: Using Web.config transformation toolset for config files in sub-folders within the project
All of the above discussion directly applies to any web.config file present in sub folders of your project (e.g. if you have a separate web.config file for say “Admin” folder then VS 10 will support transforms for them too). You can add transform files within sub-folders and use the same packaging functionality mentioned in all of the above steps to create transformed web.config files for web.config files specific to the sub folders within your project.
I think this has become a rather long post; but I hope it helps!!
Vishal R. Joshi | Program Manager | Visual Studio Web Developer
PingBack from http://microsoft-sharepoint.simplynetdev.com/web-deployment-webconfig-transformation/
We have earlier discussed about Web Deployment and Web Packaging quite a bit, today I wanted to dive
Does this work on other *.config files, too? E.g. can I transform my own externalized "appSettings.config" as well?
There will be extensibility available for you to be able to modify the externalized "appSettings.config" file... I will eventually write a blog on how to do that as it will require manually editing the web.config file...
This is a very nice feature, and one that I am looking forward to. Is there any chance that the MSBuild task will be made available separately from the whole .NET 4.0 and Visual Studio 2010 release? We will not adopt .NET 4.0 but it would be great to use these transformations in our deployment.
Also, are these transformations based on any kind of standard? If so, the community could build their own task for this (probably without the Visual Studio integration, but still useful).
Again, great feature, thanks!
It is so cool! After this support, we can maintain several web.config for debug, release, test, daily build and so on!
Thank you for submitting this cool story - Trackback from DotNetShoutout
This is a much welcomed improvement over the days of VS.NET 2005 and using Web Deployment Projects. Don't get me wrong, while this has always worked for me in the past change is always welcome. I have always used the following and it has served me well.
<!--Web.config Copy and Replace -->
<Copy Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' " SourceFiles="$(SourceWebPhysicalPath)\Web.config.SandBox" DestinationFiles="$(OutputPath)\Web.config" />
There is a MsBuild task which will run even if your site is not a .NET 4.0 site... This comes with VS 2010 so as long as you are using VS 2010 to develop your .NET 2.0/3.0 or 3.5 web you should be good there... As for any task or target file as long as you can copy them anywhere you want they should run independent of even VS... Although at this time the task is compiled using .NET 4.0 hence you will need .NET 4.0 on the box even if your site might be targeting 3.5...
Yes the transforms and locators are extensible so you can write custom transforms and locators, I will eventually write a post on that too...
If you were asking whether you can write an MsBuild task for it, then the answer is that all the code for transformation engine, transforms and locators is already part of the same dll which has the MsBuild task; so hopefully you will not have to write a seperate one...
Get trained on Visual Studio 2010 and .NET Framework 4.0 – Today! eek! If you missed it, the team that
Visual Studio 2010 has support for multiple web.config files. It is one feature of new web application
This article is giving us very good knowledge of 4.0 framework. Really Nice
以前 kkamegawa さんのところでこんなエントリがあって、 ～.configってファイルをセットアップにまぜるとき Visual Studio 2008 Web Deployment Projects か MSBuild CommunityTasks の XmlMassUpdate の記事が NAgile さんと NAndu さんの記事にあるよーなんて話をしてたんだけれど、Visual Web Developer Team Blog に Visual Studio 2010 でデ...
Thank you for adding this feature. It's a bit overdue IMHO, but better later than never. I gave up on using the "Publish Web Site" feature inside VS long ago because it was just annoying having to muck through my web.config to swap out connection strings and so forth when going from staging to prod. I am hopeful that the web.config transformation feature coming in VS2010 will be compelling enough to bring me back to doing deployment directly inside the VS IDE. Currently I use Nant-Gui for deployment. I never had much success with VS 2008 Web Deployment Projects.
Recently I wrote about Visual Studio 2010 and multiple web.config files support. Let’s see now how to