<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Customizing web.config for different environments</title><link>http://msmvps.com/blogs/egoldin/archive/2008/03/16/customizing-web-config-for-different-environments.aspx</link><description>This is a very common scenario. You develop your application in environment A. The production will run in environment B. There will be also a demo site in environment C and a test site in environment D. The environments may have different connection strings</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: Customizing web.config for different environments</title><link>http://msmvps.com/blogs/egoldin/archive/2008/03/16/customizing-web-config-for-different-environments.aspx#1702853</link><pubDate>Sat, 18 Jul 2009 19:20:28 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1702853</guid><dc:creator>Mason</dc:creator><description>&lt;p&gt;The maintenance nightmare is the requirement. Pay attention.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1702853" width="1" height="1"&gt;</description></item><item><title>re: Customizing web.config for different environments</title><link>http://msmvps.com/blogs/egoldin/archive/2008/03/16/customizing-web-config-for-different-environments.aspx#1700184</link><pubDate>Mon, 13 Jul 2009 17:52:38 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1700184</guid><dc:creator>Bruce</dc:creator><description>&lt;p&gt;Maintenance Nightmare because you have too many connection files to keep track of. What happens if you overwrite one. Plus, you can only keep one copy of the connection file in source safe. It would be better, simpler, and easier to maintain if you&amp;#39;re application would &amp;quot;sense&amp;quot; the environment, then select the appropriate environment specific configuration section. This means you only need one configuration file with sections and settings for each environment.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1700184" width="1" height="1"&gt;</description></item><item><title>re: Customizing web.config for different environments</title><link>http://msmvps.com/blogs/egoldin/archive/2008/03/16/customizing-web-config-for-different-environments.aspx#1628806</link><pubDate>Thu, 29 May 2008 15:40:30 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1628806</guid><dc:creator>Stephanie</dc:creator><description>&lt;p&gt;Thanks for the input. Interesting idea I am going to have to try.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1628806" width="1" height="1"&gt;</description></item></channel></rss>