MSDN whitepaper on deploying Microsoft .NET Framework 3.0

Through Jason Zander's blog I found a good white paper on MSDN article titled "Deploying Microsoft .NET Framework Version 3.0".

It details how the .NET Framework 3.0 (fka WinFX) relates to the .NET Framework 2.0 and where the various components are installed. I noted a couple of inconsistencies with how the .NET Framework 2.0 is deployed:

  1. Components shared with .NET Framework 2.0 are installed in the following location: %windir%Microsoft.NETFrameworkV2.0.50727

    Components that are new to .NET Framework 3.0 are installed in the following location: %windir%Microsoft.NETFrameworkV3.0

    So the build number is gone from the directory name.

  2. You can look for a specified registry key value to detect whether
    the .NET Framework is installed on a computer. The following table
    lists the registry keys and values that you can test to determine
    whether specific versions of the .NET Framework are installed.


    Registry Key Name




    InstallSuccess (DWORD value = 1)



    Install (DWORD value = 1)

    As you can see, the key name has changed from Install to InstallSuccess , it is nested one level deeper (inside Setup) and you can no longer determine the build number.

  3. The user-agent string for Internet Explorer does include the full version version when .NET Fx 3.0 is installed. It contains even more information (the revision number) than the identifier for other .NET Fx versions:

    Mozilla/4.0 (compatible; MSIE 6.0;
    Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04131.06)

    However, there is no CLR 3.0! Since this release the CLR version number is no longer coupled to the .NET Framework version number. .NET Fx 3.0 uses CLR 2.0.

    Why could other naming schemes be changed to further progress and why is this identifier not corrected?

I wish Microsoft had released this white paper simultaneuously with the WinFX rename announcement. That would have prevented a lot of confusion.

I haven't installed the .NET Framework 3.0 June CTP yet, because no compatible build of Expression Interactive Designer has been released yet. So I cannot determine if the information in the white paper is completely accurate.

Leave a Reply

Your email address will not be published. Required fields are marked *