Ok. I feel a little silly but the solution is that I didn’t need to specify a xdt:Locator. If I just leave the App.Release.Config like this it will replace matching entry. <parameter value=”data source=dbserver;Integrated Security=SSPI;Initial Catalog=someDb;MultipleActiveResultSets=true” xdt:Transform=”Replace”/> </parameters>
Web.config transformations as they are defined in the Web.Release.config are only done when deploying/publishing the project for the relevant configuration. Just changing the active configuration in Visual Studio to Release and running the application does not run the transformations. Therefore, the web.config remains unchanged. This behavior is reasonable by the way as a web application … Read more
For me I found the issue was that the slow cheetah property group in the config file was below the section where it checked if it existed. So the fix was simply to move the property group above that line somewhere which would allow the transform to run as expected. Put this: <PropertyGroup Label=”SlowCheetah”> <SlowCheetahToolsPath>$([System.IO.Path]::GetFullPath( … Read more
Transformation will only happen if you put proper xdt attributes on the elements that need to be transformed. Try adding an xdt:Transform attribute to your release config: <system.webServer xdt:Transform=”Replace”> <!– the rest of your element goes here –> </system.webServer> That will tell the transformation engine that the entire system.webServer element from Web.config needs to be … Read more
Use xdt:Transform=”InsertIfMissing” with the XmlTransform task in VS2012. It doesn’t look like Microsoft has updated their documentation to reflect this yet.
I was looking for similar information and didn’t quite find it, so I did some digging around in the .targets files that come with Visual Studio 2010 and MSBuild 4.0. I figured that was the best place to look for the MSBuild task that would perform the transformation. As far as I have been able … Read more
This will remove a specific connection string based on its name. <configuration> <connectionStrings> <add name=”ConnStr2″ xdt:Transform=”Remove” xdt:Locator=”Match(name)” connectionString=” ” /> </connectionStrings> </configuration> Note that the connectionString value is not empty string, but is instead a space. Any non-empty value would do.
The Web.config transforms are only applied as part of a publish operation. If you wish this to be done as part of an app.config build operation, then you can use the SlowCheetah – XML Transforms Visual Studio plugin: http://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5
You can use the Insert transformation: <resizer> <plugins> <add name=”AzureReader” connectionString=”DataConnectionString” xdt:Transform=”Insert” /> </plugins> </resizer> Web.config Transformation Syntax for Web Application Project Deployment
In conjunction with xdt:Transform=”Remove” use xdt:Transform=”InsertIfMissing” in VS2012. <authorization xdt:Transform=”Remove” /> <authorization xdt:Transform=”InsertIfMissing”> <deny users=”?”/> <allow users=”*”/> </authorization>