<?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>Vapor Blog : .net 3.0 2.0 upgrade wpc wcf wf installation issues known</title><link>http://msmvps.com/blogs/alvin/archive/tags/.net+3.0+2.0+upgrade+wpc+wcf+wf+installation+issues+known/default.aspx</link><description>Tags: .net 3.0 2.0 upgrade wpc wcf wf installation issues known</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>.NET 3.0 compatibility issues</title><link>http://msmvps.com/blogs/alvin/archive/2007/04/07/net-3-0-compatibility-issues.aspx</link><pubDate>Fri, 06 Apr 2007 23:28:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:762856</guid><dc:creator>vapordan@hotmail.com</dc:creator><slash:comments>0</slash:comments><description>For the most part, the conversion from .NET 2.0 to 3.0 occurs without issue. After upgrading, applications run without issue. However, I've seen some one instance where the upgrade process can corrupt the .NET 2.0 machine.config files resulting in ASP...(&lt;a href="http://msmvps.com/blogs/alvin/archive/2007/04/07/net-3-0-compatibility-issues.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://msmvps.com/aggbug.aspx?PostID=762856" width="1" height="1"&gt;</description><category domain="http://msmvps.com/blogs/alvin/archive/tags/.net+3.0+2.0+upgrade+wpc+wcf+wf+installation+issues+known/default.aspx">.net 3.0 2.0 upgrade wpc wcf wf installation issues known</category></item></channel></rss>