With Visual Studio 2010 when you package your application using the Build Deployment Package context menu option, see image below.<\/p>\n
![](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2010\/11\/6371.BuildDeployPackage.png\")
<\/p>\n
When build the package by default the package will be created in obj{Configuration}Package{ProjectName}.zip where {Configuration} is the current build configuration, and {ProjectName} is the name of the project. So in this case I since I’m building with Debug and the project name is MvcApplication1 the package will be placed at objDebugPackageMvcApplication1.zip<\/strong>. If you take this package and then import into IIS 7 with the “Import Application” option shown below. Note: The machine must have the Web Deployment Tool<\/a> (aka MSDeploy) installed.<\/p>\n Once you click on Import Application then browse out to the package you will be shown a screen which prompts your for parameters. Its shown below.<\/p>\n <\/p>\n On this screen you can see that we are prompting for a couple parameter values here. One is an IIS setting, Application Path, and the other is a connection string which will be placed inside the web.config file. If your Web Application Project (WAP) had 5 different connection strings then they would automatically show up here on this page. Since connection strings are replaced so often we create parameters for all connection strings by default. You can define new parameters on your own, quite easily actually, but that is the topic for another blog post.<\/p>\n Now back to the question. He is asking why do we “tokenize” the connection strings in web.config. To clarify take a look at my web.config file below.<\/p>\n <<\/span>configuration<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>appSettings<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>add<\/span> <\/span>key<\/span>=<\/span>“setting01<\/span>“ <\/span>value<\/span>=<\/span>“value01<\/span>“\/><\/span><\/span><\/p>\n <\/span><\/<\/span>appSettings<\/span>><\/span><\/span><\/p>\n <\/span><\/p>\n <\/span><<\/span>connectionStrings<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>add<\/span> <\/span>name<\/span>=<\/span>“ApplicationServices<\/span>“<\/span><\/p>\n <\/span><\/span>connectionString<\/span>=<\/span>“data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true<\/span>“<\/span><\/p>\n <\/span><\/span>providerName<\/span>=<\/span>“System.Data.SqlClient<\/span>“ \/><\/span><\/span><\/p>\n <\/span><\/<\/span>connectionStrings<\/span>><\/span><\/span><\/p>\n <\/span><\/p>\n <\/<\/span>configuration<\/span>><\/span><\/p>\n After I perform a package this will get changed. Take a look @ the web.config file which resides in the package (you can get to the file at obj{CofigurationName}PackagePackageTmpweb.config). You will see what is shown below.<\/p>\n <<\/span>configuration<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>appSettings<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>add<\/span> <\/span>key<\/span>=<\/span>“setting01<\/span>“ <\/span>value<\/span>=<\/span>“value01<\/span>“\/><\/span><\/span><\/p>\n <\/span><\/<\/span>appSettings<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>connectionStrings<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>add<\/span> <\/span>name<\/span>=<\/span>“ApplicationServices<\/span>“<\/span><\/p>\n <\/span><\/span>connectionString<\/span>=<\/span>“$(ReplacableToken_ApplicationServices-Web.config Connection String_0)<\/span>“<\/span><\/p>\n <\/span><\/span>providerName<\/span>=<\/span>“System.Data.SqlClient<\/span>“ \/><\/span><\/span><\/p>\n <\/span><\/<\/span>connectionStrings<\/span>><\/span><\/span><\/p>\n <\/span><\/p>\n <\/<\/span>configuration<\/span>><\/span><\/p>\n So his question is why is the connection string replaced with $(ReplacableToken_ApplicationServices-Web.config Connection String_0) and nothing else is? We do this because we do not want you to accidently copy your web to a location and have it executing SQL statements against a SQL server which you did not intend. The idea is that you will create a package that you can deploy to many different environments. So the value that was in your web.config (or web.debug.config\/web.release.config if you are using a web.config transformation<\/span><\/strong><\/a>) will not be placed inside the web.config in the package. Instead those values will be used as defaults in the package itself. We also create a SetParameters.xml file for you so that you can tweak the values. For my app see the MvcApplication1.SetParameters.xml file below.<\/p>\n <?<\/span>xml<\/span> <\/span>version<\/span>=<\/span>“1.0<\/span>“ <\/span>encoding<\/span>=<\/span>“utf-8<\/span>“?><\/span><\/span><\/p>\n <<\/span>parameters<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>setParameter<\/span> <\/span>name<\/span>=<\/span>“IIS Web Application Name<\/span>“<\/span><\/p>\n <\/span><\/span>value<\/span>=<\/span>“Default Web Site\/MvcApplication1_deploy<\/span>“ \/><\/span><\/span><\/p>\n <\/span><<\/span>setParameter<\/span> <\/span>name<\/span>=<\/span>“ApplicationServices-Web.config Connection String<\/span>“<\/span><\/p>\n <\/span><\/span>value<\/span>=<\/span>“data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true<\/span>“ \/><\/span><\/span><\/p>\n <\/<\/span>parameters<\/span>><\/span><\/span><\/p>\n The idea is that you can deploy your package in 2 ways. Through the IIS Manager which will prompt you for the parameters or you can deploy using msdeploy.exe with the –setParamFile switch to specify the path to the SetParameters.xml file. In this case I could create a QA01.SetParameters.xml file along with a QA02.SetParameters.xml file to deploy my web to my two QA servers. How do we do this?<\/p>\n You might be wondering how the connection strings are tokenized to begin with. With Visual Studio 2010 we released web.config transformations, which all you to write terse web.config transformations inside of files like web.debug.config\/web.release.config. When you package\/publish your web these transform files are used to transform your web.config based on what you expressed in the appropriate transform file. We have an MSBuild task TransformXml which performs the transformation. We use that same task to tokenize the connection strings. If you are interested in the details take a look at %ProgramFiles32%MSBuildMicrosoftVisualStudiov10.0WebMicrosoft.Web.Publishing.targets in the AutoParameterizationWebConfigConnectionStringsCore<\/strong> target.<\/p>\n Now what if you do not want the connection string tokenized?<\/p>\n If you want to prevent your web.config connection strings from being tokenized it’s pretty easy. All we need to do is the add a property to the build\/package\/publish process. We can do that in 2 ways. Edit the project file itself or create a file with the name {ProjectName}.wpp.targets where {ProjectName} is the name of your project. The second approach is easier so I use that. In my case it would be MvcApplication1.wpp.targets. The contents of the file are shown below.<\/p>\n <?<\/span>xml<\/span> <\/span>version<\/span>=<\/span>“1.0<\/span>“ <\/span>encoding<\/span>=<\/span>“utf-8<\/span>“?><\/span><\/span><\/p>\n <<\/span>Project<\/span> <\/span>xmlns<\/span>=<\/span>“http:\/\/schemas.microsoft.com\/developer\/msbuild\/2003<\/span>“><\/span><\/span><\/p>\n <\/span><\/p>\n <\/span><<\/span>PropertyGroup<\/span>><\/span><\/span><\/p>\n <\/span><<\/span>AutoParameterizationWebConfigConnectionStrings<\/span>><\/span>false<\/<\/span>AutoParameterizationWebConfigConnectionStrings<\/span>![](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2010\/11\/2860.ImportApp.png\")
<\/p>\n![](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2010\/11\/5224.Iis-Parameters.png\")
<\/p>\n How connection strings are tokenized<\/h3>\n
Prevent tokenizing connection strings<\/h3>\n