<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Azure Miniseries #3: ServiceConfig vs web.config</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/dpeeast/Azure-Miniseries-3-ServiceConfig-vs-webconfig/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/530788_100x75.jpg</url>
		<title>Channel 9 - Azure Miniseries #3: ServiceConfig vs web.config</title>
		<link></link>
	</image>
	<description>In this screencast, I&#39;ll show some strategies when working with Azure webroles and handling settings -- particularly connection strings -- in both the ServiceConfiguration and web.config files.&amp;nbsp; Traditionally, we&#39;ve always used the web.config for all of
 our website settings.&amp;nbsp; While we can do that in the cloud, all files (including the web.config) are read-only as part of the deployment; in order to change them, we&#39;d need to redeploy our application.&amp;nbsp; The goal, then, is to migrate key settings to the ServiceConfiguration
 file.&amp;nbsp; For some settings -- particularly SQL Membership Provider connection strings -- this can be challenging but not impossible!
</description>
	<link></link>
	<language>en</language>
	<pubDate>Thu, 23 May 2013 01:24:59 GMT</pubDate>
	<lastBuildDate>Thu, 23 May 2013 01:24:59 GMT</lastBuildDate>
	<generator>Rev9</generator>
</channel>
</rss>