.NET Framework 1.1 deployment guide

There is a pretty good document published on MSDN that provides a technical overview of various topics related to deploying the .NET Framework 1.1.  It provides information related to mass-deployment to a network of computers, and also information related to redistributing the .NET Framework 1.1 as part of another setup package (for managed applications that want to bootstrap the .NET Framework if it is not installed instead of blocking and forcing the user to install it themselves).

You can find this article at this location.  Here are a few of the important topics covered in this article:

  1. How to deploye the .NET Framework 1.1 via SMS (listed in the section named "Deploying the .NET Framework using Systems Management Server")

  2. How to deploye the .NET Framework 1.1 via Active Directory (listed in the section named "Deploying the .NET Framework using Active Directory")

  3. Detecting whether or not the .NET Framework 1.1 is installed (listed in the section named "Detecting that the .NET Framework 1.1 is installed")

  4. Detecting whether or not .NET Framework 1.1 language packs are installed (listed in "Table 2. .NET Framework Registry Locations")

  5. How to determine whether or not installing the .NET Framework 1.1 succeeded when it is chained as part of another product's setup package (there is a list of options in the section named "How to Determine If the .NET Framework, J# Redistributable Package, or Language Pack Installed Successfully From a Setup Package That Installs It As a Prerequisite")

Now if I can only get all of the setup developers inside of Microsoft who redistribute the .NET Framework to follow these guidelines, I'll be making some progress.  I see way too many cases where setup developers choose random registry values or files and start using them to detect the presence or absence of the .NET Framework.  Invariably, if someone follows undocumented strategies and relies on behaviors that are observed but not officially supported, it can lead to compatibility issues when later versions of the .NET Framework are released if the behaviors are changed.  Microsoft product teams will not scrutinize or question behavior changes as much if they are not publicly documented because they tend to assume that others (inside and outside of Microsoft) will rely on officially documented behaviors when designing their own solutions.

<update date="1/14/2009"> Fixed broken link to the .NET Framework 1.1 deployment guide on MSDN. </update>


Comments (4)
  1. Stephane Rodriguez says:

    Questionable is why this remains "only" guidelines while it could be implemented in a shared dll with an deterministic API available to anyone.

  2. Ian Thomas says:

    Here’s a stop-gap tool for developers – but in my view, the whole prerequisites thing is a dog’s breakfast, and it’s about time that a REAL solution was put in place.

    "Microsoft Component Installer Software Development Kit (Spring 2005)"

    MicrosoftComponentInstallerSDKforWindows.exe – 1271 KB (5/23/2005)

    Version: Spring




    Microsoft Component Installer Software Development Kit (Spring 2005) helps you deliver the needed Windows component to your customer in order to run your application. The SDK provides support for installing any or all of the following components (in the following order):

    * Microsoft Data Access Components (MDAC) 2.8

    * Microsoft .NET Framework 1.1

    * Microsoft DirectX 9.0c

    * Microsoft DirectX 9.0c for Managed Code

    * Microsoft .NET Framework Version 1.1 Language Pack

    * Microsoft .NET Framework 1.1 Service Pack 1

    * Microsoft ASP.NET Security Update for Microsoft .NET Framework 1.1 Service Pack 1

    * Microsoft Windows Installer 2.0

    * Microsoft Windows Installer 3.1

    The resulting user experience (sic!!) is a small application they can download and run (or run from a CD). It provides the user with a simple wizard user interface that has details on the components that are needed and on the progress of the installation. The customer experience is already localized for over 20 Windows languages and will auto-detect the system locale at launch and will adjust its language as appropriate.

    System Requirements / Supported Operating Systems: Windows 2000, Windows 98 Second Edition, Windows ME, Windows XP, Windows XP Tablet PC Edition

    The components installed determine the needed minimal requirements of the target computer. Since they are selectable, you need to communicate those to your customer.

  3. Hi Franklesniak – Thanks for the link.  I’ve updated the main text of this blog post to point to the new location for this deployment guide.

Comments are closed.

Skip to main content