<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Offline and the "CONFIG FILE" Issue</title><link>http://blogs.msdn.com/b/eric_carter/archive/2006/09/22/766586.aspx</link><description>A reader posted this question to me: 
 "I developed an Outlook plugin... 
 I add the application manifest file in my setup project and deployed on client machine and published it on a deployment server. the problem is that when deployment server is</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Offline and the &amp;amp;quot;CONFIG FILE&amp;amp;quot; Issue</title><link>http://blogs.msdn.com/b/eric_carter/archive/2006/09/22/766586.aspx#766754</link><pubDate>Fri, 22 Sep 2006 22:31:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:766754</guid><dc:creator>Josh Einstein</dc:creator><description>I don't get it. Why can't it just assume that there was no configuration file? How is the current behavior any better than that? In the current behavior, you could just as easily have an outdated config file, right? I'm sure I'm missing something though.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=766754" width="1" height="1"&gt;</description></item></channel></rss>