StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POManaging complex Web.Config files between deployment environments
primarykey
Id
428573
data
AcceptedAnswerId
435082
AnswerCount
11
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-09T15:50:19.593
FavoriteCount
32
LastActivityDate
2017-04-11T07:12:28.423
LastEditDate
2015-07-02T12:18:30.370
LastEditorUserId
2630337
OwnerUserId
28278
ParentId
0
PostTypeId
1
Score
53
ViewCount
19576
LastEditorDisplayName
rally25rs
text
Body
Does anyone know of any good tools/utilities for managing <code>Web.Config</code> files between different build/deployment environments? For example, I have a WCF project that in development I don't want to enable SSL, but I do want it enabled in production. I want different logging settings, different DB connection strings, different error handling, different file paths... Even some different Unity framework bindings (wire up mocks for unit testing instead of the real objects for deployment). Maintaining individual copies of the <code>Web.Config</code> is a pain, because adding a new web service means editing multiple files and keeping them in sync. I've also noticed that if you muck with the <code>Web.Config</code> too much by hand, Visual Studio will choke if you try to use the "add item" wizard to, say, add a new Web Service for WCF, since it has to modify the Web.Config to add the endpoint,a nd can't parse it any more. So I have to be careful not to invalidate the existing Web.Config. I also thought about just using some regex to do replacements and just building a new <code>Web.Config</code> in a pre-build command. That seems like the best option so far... Any other ideas? It seems like this should be a very common issue, since the <code>Web.Config</code> should probably never be the same between development and production deployments. <hr> Update: I decided to write a quick console app that will take all the xml files in a given directory and merge them into one, and only include certain files based on the name. So I can make in a directory: WebConfig_All <pre><code><configuration> <configSections> ... </configSections> <system.web> ... </system.web> </configuration> </code></pre> connectionStrings_Debug <pre><code><configuration> <connectionStrings> <add name="connstr" connectionString="...dev..." /> </connectionStrings> </configuration> </code></pre> connectionStrings_Release <pre><code><configuration> <connectionStrings> <add name="connstr" connectionString="...prod..." /> </connectionStrings> </configuration> </code></pre> Then run my command line tool, and pass in the configuration (Debug, Release, custom...) And it will merge all the files that end in <code>_All" or</code>_<configuration>`. So now I have 80% of my Web.Config in a single <code>WebConfig_All</code> file, and the 20% custom stuff in separate files per build configuration. I can then run my command line tool as a pre-build task in VisualStudio, or from NAnt, or wherever I want... I also made my XML merge logic good enough to handle stuff like: <pre><code><x> <y a="1"> <z a="1"/> </y> </x> </code></pre> merge with <pre><code><x> <y a="1"> <z a="2"/> </y> <y a="2"/> </x> </code></pre> results in: <pre><code><x> <y a="1"> <z a="1"/> <z a="2"/> </y> <y a="2"/> </x> </code></pre> Looking good so far... :) <hr> Followup: This topic is a little old now, so I wanted to point out that VisualStudio 2010 has a feature to do web.config transformations built-in: <a href="http://msdn.microsoft.com/en-us/vstudio/Video/ff801895" rel="noreferrer">http://msdn.microsoft.com/en-us/vstudio/Video/ff801895</a> Of course in typical Microsoft fashion of only implementing any feature 50% of the way, it only works for web projects using web deploy. There is a plugin to enable transformations in other projects, located here: <a href="http://www.hanselman.com/blog/SlowCheetahWebconfigTransformationSyntaxNowGeneralizedForAnyXMLConfigurationFile.aspx" rel="noreferrer">http://www.hanselman.com/blog/SlowCheetahWebconfigTransformationSyntaxNowGeneralizedForAnyXMLConfigurationFile.aspx</a> You could also use a tool like <a href="http://inedo.com/buildmaster/overview" rel="noreferrer">BuildMaster</a> to manage config files (along with builds, tests, DB scripts, etc...)
Tags
<.net><asp.net><visual-studio><wcf>
Title
Managing complex Web.Config files between deployment environments
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRobert
UserOwnerUserId
1. USCodingWithSpike
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POManaging complex Web.Config files between deployment environments
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POManaging complex Web.Config files between deployment environments
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POManaging complex Web.Config files between deployment environments
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.