<?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 : CLR requiredruntime version 3.5 .NET</title><link>http://msmvps.com/blogs/alvin/archive/tags/CLR+requiredruntime+version+3.5+.NET/default.aspx</link><description>Tags: CLR requiredruntime version 3.5 .NET</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>RequiredRuntime fails for targetting CLR versions</title><link>http://msmvps.com/blogs/alvin/archive/2007/10/26/requiredruntime-fails-for-targetting-clr-versions.aspx</link><pubDate>Fri, 26 Oct 2007 14:38:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1265356</guid><dc:creator>vapordan@hotmail.com</dc:creator><slash:comments>1</slash:comments><description>Recently, I walked right into an ambush with .NET. A client asked how best to target a CLR version from a .NET application. Easy right? Just use this in an app.config file: &amp;lt;startup&amp;gt; &amp;lt;requiredRuntimeversion=&amp;quot;v1.0.3705&amp;quot; safemode=&amp;quot;true&amp;quot;...(&lt;a href="http://msmvps.com/blogs/alvin/archive/2007/10/26/requiredruntime-fails-for-targetting-clr-versions.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1265356" width="1" height="1"&gt;</description><category domain="http://msmvps.com/blogs/alvin/archive/tags/CLR+requiredruntime+version+3.5+.NET/default.aspx">CLR requiredruntime version 3.5 .NET</category></item></channel></rss>