<?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>MZ-Tools Articles Series: HOWTO: Get the target .NET Framework of a Visual Studio 2008 project from a Visual Studio add-in or macro</title><link>http://msmvps.com/blogs/carlosq/archive/2008/06/05/mz-tools-articles-series-howto-get-the-target-net-framework-of-a-visual-studio-2008-project-from-a-visual-studio-add-in-or-macro.aspx</link><description>Today I had to get the target .NET Framework of a VS 2008 project. While the project file stores the values as &amp;quot;v2.0&amp;quot;, &amp;quot;v3.0&amp;quot;, etc, the values returned by the automation model are a bit surprising at first glance. Here is the article</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Visual Studio Links #37</title><link>http://msmvps.com/blogs/carlosq/archive/2008/06/05/mz-tools-articles-series-howto-get-the-target-net-framework-of-a-visual-studio-2008-project-from-a-visual-studio-add-in-or-macro.aspx#1631708</link><pubDate>Thu, 05 Jun 2008 15:55:27 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1631708</guid><dc:creator>Visual Studio Hacks</dc:creator><description>&lt;p&gt;My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. US ISV Developer Evangelism Team has posted a link to 46 tutorials that the ASP.NET team has created for the ASP.NET AJAX Control&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1631708" width="1" height="1"&gt;</description></item></channel></rss>