Deployment to a Hosting Provider: Web.Config File Transformations - 3 of 12http://asp.netWed, 16 May 2012 15:11:42 GMTumbracoComments for Deployment to a Hosting Provider: Web.Config File Transformations - 3 of 12enComment Posted by nivram509http://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Fri, 24 Feb 2012 15:48:39 GMT00000000-0000-0000-0000000014935"Open Web.Release.config and add the following code immediately following the appSettings element that you added earlier."

Does that mean after </appSettings> or after the <add key...>? Either could be considered the appSettings element I added earlier.

]]>Comment Posted by nivram509http://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Fri, 24 Feb 2012 16:32:45 GMT00000000-0000-0000-0000000014936All of my builds (Dev, Test, & Release) say (Dev) at the top. Does this mean I've done something wrong? Do I need to do something to get Web.Test.config and Web.Release.config to work when I change my build settings in the Configurations Manager?

Here's my <appsettings> from my Web.Test.config

<appSettings>

<add key="DatabaseInitializerForType ContosoUniversity.DAL.SchoolContext, ContosoUniversity.DAL"

value="Disabled" xdt:Transform="SetAttributes" xdt:Locator="Match(key)"/>

<add key="Environment" value="Test" xdt:Transform="SetAttributes" xdt:Locator="Match(key)"/>

</appSettings>

]]>Comment Posted by nivram509http://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Sat, 25 Feb 2012 15:00:34 GMT00000000-0000-0000-0000000014943To answer my own questions (in case anyone else wonders):

1. After </appSettings>

2. The transforms seem to happen on deploy, not build. Keep going with the tutorial, and you'll see them work.

]]>Comment Posted by tdykstrahttp://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Fri, 09 Mar 2012 13:46:41 GMT00000000-0000-0000-0000000015074@nivram509 - Thanks for the comments -- in the next release of the tutorial I'll change the wording of "immediately following the appSettings element" to "immediately following the </appSettings> closing tag." I'll also add an explanation about when the transformations are actually applied.

]]>Comment Posted by kaelumhttp://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Thu, 26 Apr 2012 15:10:41 GMT00000000-0000-0000-0000000015418This article is pretty good, but it does introduce a serious security issue that circumvents the entire QA/UAT/Production deployment system. By allowing an "Environment" setting you are also allowing anyone to write code that will only execute in a specific environment, including maliscious code.

Way back in 2002, a Microsoft ASP.NET architect brought up the idea and community immediately pointed out the issue. This was going to be a new setting in the machine.config, but after a month on negative publicity Microsoft agreed to not release the change.

]]>Comment Posted by tdykstrahttp://asp.net/mvc/tutorials/deployment/deployment-to-a-hosting-provider/deployment-to-a-hosting-provider-web-config-file-transformations-3-of-12Wed, 16 May 2012 15:11:42 GMT00000000-0000-0000-0000000015531@kaelum - Thanks for the comment. The environment setting in this case doesn't cause code to execute, it's for display purposes only, and it illustrates how to handle a common scenario, e.g., when you need to update WCF endpoints in different environments.

]]>