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>
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
Add xdt:Transform=”Replace” to your .release <system.net> <mailSettings> <smtp deliveryMethod=”Network” xdt:Transform=”Replace”> <network host=”smtp.mysite.com” userName=”myuser” password=”mypassword” /> </smtp> </mailSettings> </system.net>
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>