Microsoft .NET Framework 2.0 Service Pack 1, and How to Detect It

Microsoft .NET Framework 2.0 Service Pack 1, and How to Detect It

  • Comments 23

No doubt you've heard the Microsoft .NET Framework 3.5 was released. Aaron Stebner has posted a list of links to 3.5, as well as 2.0 Service Pack 1 (SP1) and 3.0 SP1. It's important to note that if you install 3.5 you're actually getting 2.0 SP1 and 3.0 SP1 both.

The .NET Framework 3.5 consists of the following:

  • Microsoft .NET Framework 2.0 Service Pack 1, which runs on the 2.0 version of the Common Language Runtime (CLR)
  • Microsoft .NET Framework 3.0 Service Pack 1, which runs on the 2.0 version of the CLR and adds Windows CardSpace, the Windows Communication Foundation (WCF), the Windows Presentation Foundation (WPF), and the Windows Workflow Foundation (WF)
  • Microsoft .NET Framework 3.5, which runs on the 2.0 version of the CLR and adds support for LINQ and lots of other new classes

While 2.0 SP1 and 3.0 SP1 are actually full major upgrades that will replace older versions if installed, they update the SP detection keys as documented previously. The registry detection keys we introduced in .NET Framework 3.0 and Visual Studio 2005 will not work for 2.0 SP1 and 3.0 SP1, unfortunately, until at least one patch is installed that will add them in. If you're using the NetFxExtension with WiX, however, to add the AppSearch property NETFRAMEWORK20_SP_LEVEL or NETFRAMEWORK30_SP_LEVEL you'll be fine. These use the older detection keys that will continue to work as documented.

Leave a Comment
  • Please add 8 and 5 and type the answer here:
  • Post
  • A reader pointed out that the list of fixes for .NET Framework 2.0 Service Pack 1 were published. I also

  • Matthew, please report bugs at http://connect.microsoft.com/visualstudio.

  • I just ran into an issue with .NET 2.0 SP1 too.  MS changed the product code with the service pack.  That bungles all our .NET 2.0 product detection scripts.  It's really frustrating.  

  • lge, Microsoft has never condoned that I've seen detecting .NET based on MSI properties. Fact is, even starting with .NET 1.0 it has never been deployed solely using MSI. .NET 1.0 was deployed via update.exe in Tablet PC and Media Center editions, and .NET 1.1 was using update.exe in Win2K3. In Vista, .NET 2.0 and 3.0 (both SP1 as well) use CBS. For both CBS and OCM cases, checking against a ProductCode will never work.

    You should use the registry keys for detection only.

  • I am getting detection issues in 2 areas: after installing 2.0 which was REQUIRED for SQL (which installed and ran/accessed just fine) I the installed MS Great Plains, it says "2.0 not detected, please install", the fix seemed to be NOT to install the already installed 2.0 but to delete 1.0, so I did and GP installed but doesnt' run (getting Stop 0x00...5), so now i am trying to uninstall (remove) GP using either the CD or Add/Remove programs and it says, 2.0 not detected...geez

  • .NET Framework 3.5 Info You Might Not Know

  • what does it mean "..and Visual Studio 2005 will not work for 2.0 SP1 and 3.0 SP1.."? Is it what I'm getting: Macros in vs2005 stop working after installing 2.0SP1 or up?

  • Les, the whole sentence reads, "The registry detection keys we introduced in .NET Framework 3.0 and Visual Studio 2005 will not work for 2.0 SP1 and 3.0 SP1, unfortunately, until at least one patch is installed that will add them in." This patch is about detection registry values, so I'm stating that using those registry values that have worked for previous versions will not wrk for 2.0 SP1 and 3.0 SP1.

Page 2 of 2 (23 items) 12