<?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>How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx</link><description>I have seen a few questions on the newsgroups about how to determine whether or not the .NET Framework 1.1 SP1 is installed on your machine. A colleague pointed me to a KB article that describes a method of looking at file versions to determine this.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229604</link><pubDate>Tue, 14 Sep 2004 20:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229604</guid><dc:creator>Steven Bone</dc:creator><description>Aaron - I was always frustrated by the methodology of determining the version of the .NET framework(s) that are installed.  The KB article doesn't help that much if you are trying to programatically determine the version.  Worst of all, for each release of the framework, I need to rewrite the detection code.  It would be nice if you or Microsoft provided a C++ sample that will return the appropriate installed versions that is somewhat future-proof.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229609</link><pubDate>Tue, 14 Sep 2004 20:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229609</guid><dc:creator>Stephane Rodriguez</dc:creator><description>MeThink you should explain how to take advantage of the IE user agent string when possible. Combined with the download page of some website, it can provide a more transparent experience.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229630</link><pubDate>Tue, 14 Sep 2004 21:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229630</guid><dc:creator>Aaron Stebner</dc:creator><description>Thank you for the feedback so far.  I like the idea of a code sample - I need to do a bit more research on methods of detecting 1.0 SPx before I can code that up, but stay tuned.&lt;br&gt;&lt;br&gt;Stephane - can you clarify what you mean by taking advantage of the IE user agent string in your comment?&lt;br&gt;&lt;br&gt;Thanks!&lt;br&gt;</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229755</link><pubDate>Wed, 15 Sep 2004 03:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229755</guid><dc:creator>Steven Bone</dc:creator><description>Thanks, Aaron, that would be great to get a sample together!</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229770</link><pubDate>Wed, 15 Sep 2004 04:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229770</guid><dc:creator>Uwe</dc:creator><description>Is there a KB article about &amp;quot;How to detect WHY the .NET Framework 1.1 service pack is NOT installed&amp;quot;?&lt;br&gt;&lt;br&gt;That TargetInvocationException during installation is really annoying... :-(</description></item><item><title>How to detect what .NET Framework 1.0 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229803</link><pubDate>Wed, 15 Sep 2004 09:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229803</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description /></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229820</link><pubDate>Wed, 15 Sep 2004 07:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229820</guid><dc:creator>Stephane Rodriguez</dc:creator><description>&lt;br&gt;&lt;a target="_new" href="http://blogs.msdn.com/ie/archive/2004/09/02/224902.aspx"&gt;http://blogs.msdn.com/ie/archive/2004/09/02/224902.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;When the .NET run-time is installed, IE6 is updated and it appends whatever is found in the following registry key, in the user agent string of every single web request : HKLM/Software/Microsoft/Windows/CurrentVersio/Internet Settings/5.0/User Agent/Post Platform&lt;br&gt;&lt;br&gt;</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#229908</link><pubDate>Wed, 15 Sep 2004 13:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:229908</guid><dc:creator>MichaelM</dc:creator><description>Is there a reason that the framework doesn't have a way to detect its own version?  It's damn useful to have this functionality in Windows, and it seems like it would be a no-brainer to that this would be used elsewhere.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#230067</link><pubDate>Wed, 15 Sep 2004 18:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:230067</guid><dc:creator>Steven Bone</dc:creator><description>Michael - I am sure this is possible.  I believe System.Environment.Version gives you this.&lt;br&gt;&lt;br&gt;Stephane - I think relying on the User Agent string is a bad idea.  Some people change this string using various tweaks to hide (or change) their browser version and its capabilities.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#230494</link><pubDate>Thu, 16 Sep 2004 17:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:230494</guid><dc:creator>Aaron Stebner</dc:creator><description>There are APIs within the .NET Framework to detect what its own version is, and that can be useful in some scenarios.  If you are writing a setup that is trying to bootstrap the .NET Framework, it is likely not going to work to try to make a managed code API call to detect .NET Framework version.  Also I wouldn't recommend writing a setup in managed code due to the additional complexity and possible points of failure.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#230577</link><pubDate>Thu, 16 Sep 2004 19:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:230577</guid><dc:creator>Stephane Rodriguez</dc:creator><description>&lt;br&gt;&amp;quot;Some people change this string using various tweaks to hide&amp;quot;.&lt;br&gt;&lt;br&gt;I think this is a ridiculous statement. The 0.01% people who purposedly do this get what they deserve. All others are provided a better user experience with the website able to redirect the user to a proper page, not a default one.&lt;br&gt;</description></item><item><title>Sample code to detect .NET Framework 1.0 and 1.1 and service packs</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#231255</link><pubDate>Sat, 18 Sep 2004 22:23:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:231255</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description /></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#231439</link><pubDate>Sun, 19 Sep 2004 15:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:231439</guid><dc:creator>Steven Bone</dc:creator><description>Hi Stephane,&lt;br&gt;&amp;gt;I think this is a ridiculous statement. &lt;br&gt;It certainly sounds that way, but it can be a means of exploit reduction.  If I browse with a Firefox string, I can be served up a different exploit than browsing with an IE string.  But corner-cases aside, I was referring to detecting the .NET runtime for a setup application, and I would prefer to rely on a 100% method of detecting the available versions, not 99.99%.  For web site detection, this is all you have to go on, and yes, people who change it deserve what they get.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#231969</link><pubDate>Mon, 20 Sep 2004 20:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:231969</guid><dc:creator>Stephane Rodriguez</dc:creator><description>&lt;br&gt;&amp;quot;and I would prefer to rely on a 100% method of detecting the available versions, not 99.99%&amp;quot;.&lt;br&gt;&lt;br&gt;No pun intended, but I think you need to take a look at web deployment a bit more. By reading what you say I have that feeling you haven't been doing too much of that install-from-the-web thing.&lt;br&gt;Let's get to the point : the first impression from your audience -- potentially customers -- are your web pages, and your setup. It had better be appropriate.&lt;br&gt;By being not only appropriate, but even to the point, you are setting yourself well. A seamless .NET detection minimizes the amount of round-trips, default cab and msm modules.&lt;br&gt;Even more, a seamless .NET detection reduces the amount of clicks between your home page and the user actually installing the software.&lt;br&gt;Sum up all the benefits mentioned in this thread, and compare with the ol' way of doing things.&lt;br&gt;&lt;br&gt;&lt;br&gt;</description></item><item><title>Determine if and what version of the .NET Framework is installed (including service pack levels)?</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#232513</link><pubDate>Tue, 21 Sep 2004 22:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232513</guid><dc:creator>AddressOf.com</dc:creator><description /></item><item><title>How to know which .NET framework servicepack version is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#232727</link><pubDate>Wed, 22 Sep 2004 10:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:232727</guid><dc:creator>Ed's Blog</dc:creator><description /></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#233180</link><pubDate>Thu, 23 Sep 2004 03:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:233180</guid><dc:creator>Steven Bone</dc:creator><description>Stephane, I have done web deployment.  Thanks for reminding me of the web deployment pain!  I am in complete agreement on your methodology.&lt;br&gt;&lt;br&gt;I was guilty of writing an ActiveX control to determine if I should send someone to a simple msi download or an exe that contained the MSI redistributable for their OS.  It is important to conserve as much of your potential or paying customer's 56k bandwith as possible, especially in the old days, by giving them what they need to get going and nothing more.&lt;br&gt;&lt;br&gt;Using your example of looking at browser strings, for the most part (today) this gives me the information I need to know - if the user is XP or 2k, I know they have the MSI runtimes and can behave appropriately.  As you stated, it is great for .NET applications, since this works across the board.  &lt;br&gt;&lt;br&gt;Firefox browsers don't help you determine anything - nor do they support ActiveX, so they are left with less automatically determined options.  Same with people who muck with their user agent strings.  In those cases,  I would expect the user knows what they are doing and give them a variety of download options.&lt;br&gt;&lt;br&gt;My (limited) point of view above was from that of a customer with a CD in their drive and/or a tiny web download bootstrapper application.  In those situations, I wouldn't look anywhere near the browser string.</description></item><item><title>Determine if and what version of the .NET Framework is installed (including service pack levels)?</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#233443</link><pubDate>Thu, 23 Sep 2004 19:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:233443</guid><dc:creator>AddressOf.com</dc:creator><description>I came across an excellent example that shows how to determine what editions and service pack level of the existing Microsoft .NET Framework is installed.  Unfortunately for most of my readers, this code was in C  .  I've converted the code to VB.NET for everyone to benefit ;-)</description></item><item><title>Sample code to detect .NET Framework 1.0 and 1.1 and service packs</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#245759</link><pubDate>Thu, 21 Oct 2004 19:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:245759</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description /></item><item><title>re: Determine if and what version of the .NET Framework is installed (including service pack levels)?</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#275524</link><pubDate>Mon, 06 Dec 2004 12:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:275524</guid><dc:creator>AddressOf.com</dc:creator><description /></item><item><title>Sample code to detect .NET Framework 1.0 and 1.1 and service packs</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#434004</link><pubDate>Thu, 30 Jun 2005 01:25:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:434004</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description>Hey all,&lt;br&gt;In response to some suggestions from folks who read my blog posts describing how to detect...</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#438160</link><pubDate>Wed, 13 Jul 2005 02:03:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:438160</guid><dc:creator>Jason</dc:creator><description>Does anyone have a table or can point me to a link listing .Net versions and their corresponding service packs? I haven't seen one previously.</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#438248</link><pubDate>Wed, 13 Jul 2005 06:11:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:438248</guid><dc:creator>astebner</dc:creator><description>Hi Jason - I wrote up a table listing these versions, you can find it at &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/astebner/archive/2005/07/12/438245.aspx"&gt;http://blogs.msdn.com/astebner/archive/2005/07/12/438245.aspx&lt;/a&gt;.  Hope this helps.  Let me know if you have any questions.&lt;br&gt;</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#460055</link><pubDate>Fri, 02 Sep 2005 19:54:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:460055</guid><dc:creator>Vlad Ostrovsky</dc:creator><description>I have 1.1 installed on my machine (XP SP2).  However, the registry key is totally diferent.  Any idea?</description></item><item><title>re: How to detect what .NET Framework 1.1 service pack is installed</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#460293</link><pubDate>Sat, 03 Sep 2005 02:05:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:460293</guid><dc:creator>astebner</dc:creator><description>Hi Vlad - this registry info for .NET 1.1 on XP SP2 should be the same as I describe above.  Can you let me know what the registry looks like on your machine and I can try to figure out what is going on?&lt;br&gt;&lt;br&gt;</description></item><item><title>Aaron Stebner's WebLog : What .NET Framework version numbers go with what service pack</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#1923201</link><pubDate>Wed, 21 Mar 2007 07:53:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1923201</guid><dc:creator>Aaron Stebner's WebLog : What .NET Framework version numbers go with what service pack</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/astebner/archive/2005/07/12/what-net-framework-version-numbers-go-with-what-service-pack.aspx"&gt;http://blogs.msdn.com/astebner/archive/2005/07/12/what-net-framework-version-numbers-go-with-what-service-pack.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>
Alex Lowe on Software and Technology &amp;raquo; Detecting Installed Microsoft .Net Framework (CLR) Version Information</title><link>http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx#3978522</link><pubDate>Fri, 20 Jul 2007 21:13:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3978522</guid><dc:creator>
Alex Lowe on Software and Technology » Detecting Installed Microsoft .Net Framework (CLR) Version Information</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.lowesoftware.com/software-development/detecting-installed-microsoft-net-framework-clr-version-information"&gt;http://blog.lowesoftware.com/software-development/detecting-installed-microsoft-net-framework-clr-version-information&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>