Export (0) Print
Expand All

.NET Framework Client Profile Deployment Guide

.NET Framework 3.5

Updated: August 2008

The .NET Framework Client Profile was created to address feedback from many customers that a smaller framework was needed specifically for client applications. The .NET Framework Client Profile is a subset of assemblies already contained within .NET Framework 3.5 SP1. The .NET Framework Client Profile subset is focused on fulfilling the needs of client applications.

NoteNote:

The software referenced in this document, including without limitation, the .NET Framework Client Profile, .NET Framework version 3.5, .NET Framework 3.5 SP1, and Active Directory, are each subject to license terms and conditions. These instructions assume that such license terms and conditions have been reviewed and accepted by the appropriate licensees of the software. These instructions do not waive any of the terms and conditions of such license agreements.

For Windows XP, Windows 2000, and Windows Server 2003, Windows Installer 3.1 must be installed on the computer. You can download Windows Installer 3.1 from the Windows Installer 3.1 Redistributable page on the Microsoft Download Center Web site.

This topic contains the following sections.

The .NET Framework Client Profile contains the following features. There are no new features specific to the .NET Framework Client Profile.

  • Smaller framework deployment - approximately 28 MB client deployment package.

  • Smaller, faster client deployment bootstrapper.

  • Client application focused feature set.

    • common language runtime (CLR)

    • ClickOnce

    • Windows Forms

    • Windows Presentation Foundation (WPF)

    • Windows Communication Foundation (WCF)

  • Visual Studio 2008 SP1 integration – Applications can be targeted specifically for the .NET Framework Client Profile.

The subset of assemblies in the .NET Framework Client Profile is the same as in the full installation of the .NET Framework. The .NET Framework Client Profile is organized in the same way as the .NET Framework to make sure that the functional parity is maintained. As you can see in the following illustration, the .NET Framework is a set of versioned layers that depend on the layer below it.

The .NET Framework Client Profile is deployed in the same versioned layer system as the full framework. This allows for the end-user computer to be easily upgraded to the full framework if an application requires the full framework.

Full Framework and Client Framework

The .NET Framework Client Profile deployment bootstrapper is the part of the .NET Framework Client Profile that manages the deployment of the client redistributable packages. The .NET Framework Client Profile bootstrapper is small, approximately 200 KB, and is primarily designed to support Web based deployment scenarios. The .NET Framework Client Profile bootstrapper uses XML files to allow for more flexibility of deployment configurations. As you can see in the following illustration, the .NET Framework Client Profile bootstrapper contains several XML files that determine how packages are deployed.

Client Profile Bootstrapper

The Deployment.xml file contains the definition of the user interfaces displayed to end-users when it is deployed. The file also contains references to Product.xml files that allow developers to define how an application or prerequisite is to be installed or uninstalled.

The Product.xml files contain the information necessary to install the products required by an application. The Product.xml file format follows the Product and Package Schema Reference required for ClickOnce application deployments.

The .NET Framework Client Profile is targeted for end-user configuration where no framework components are installed. Windows Vista and Windows Server 2008 already have parts of the .NET Framework installed, so client redistributable deployments on these operating systems will not be possible.

By default, Windows XP SP2 or later and Windows Server 2003 do not have any framework components installed. The .NET Framework Client Profile redistributable package can be installed on Windows XP. The .NET Framework Client Profile redistributable package cannot be installed on Windows Server 2003 as this operating system is not intended for use as a client application platform. The following table explains how each operating system is managed to make sure client applications are fully functional upon deployment.

Operating System

No .NET Framework components

.NET Framework 1.1

.NET Framework 2.0/SP1

.NET Framework 3.0/SP1

.NET Framework 3.5

Windows XP SP2 and later

Client Profile Install

Full Install

Full Install

Full Install

Full Install

Windows Vista

NA

NA

Full Install

Full Install

Full Install

Windows Server 2003

Full Install

Full Install

Full Install

Full Install

Full Install

Windows Server 2008

NA

NA

Full Install

Full Install

Full Install

Client Profile Install = .NET Framework Client Profile redistributables will be installed

Full Install = .NET Framework 3.5 SP1 full installation

As is illustrated in the previous table, the .NET Framework Client Profile deployment is focused on Windows XP SP2 and later with no .NET Framework components installed. This .NET Framework platform configuration is still the predominant .NET Framework platform configuration and will continue be so for the foreseeable future.

However, it should be noted that the end-user deployment experience for all platform configurations will continue to have the same look and consistency.

NoteNote:

The .NET Framework Client Profile will not be supported on x64 or ia64 platforms. If there are client applications that require .NET Framework for these CPU types, it is recommended that developers and users install the full .NET Framework for those platforms.

Deploying the .NET Framework Client Profile

The intent of the .NET Framework Client Profile is to allow application developers to distribute the .NET Framework Client Profile with their application deployments. Application developers can take advantage of the .NET Framework Client Profile feature that allows developers to brand, package, redistribute, and provide a consistent user experience. Therefore, it is recommended that the .NET Framework Client Profile be distributed with the client application.

If the distribution of the application does not allow for its packaging with .NET Framework Client Profile, administrators may choose to pre-install the .NET Framework Client Profile. Administrators should be aware that the .NET Framework Client Profile will detect the operating system and current version of the .NET Framework currently installed. If the current configuration does not meet the requirement needed to install the .NET Framework Client Profile payload, the full .NET Framework version 3.5 Service Pack 1 will be installed.

NoteNote:

The .NET Framework Client Profile is not intended to function with any other versions of the .NET Framework. If any version, other than the latest version of the .NET Framework, is to be installed, the .NET Framework Client Profile will halt that installation and prompt the user to install the full .NET Framework version 3.5 Service Pack 1 or later.

NoteNote:

If an unattended install of any other version of the .NET Framework is attempted while the .NET Framework Client Profile is installed, the installation will be halted. When halted, there will be a prompt for the user to install the latest version of the .NET Framework version 3.5 Service Pack 1. Administrators can work around this issue by installing .NET Framework version 3.5 Service Pack 1 instead of the older version of the .NET Framework.

For more information about deploying the .NET Framework 3.5 or later, see .NET Framework 3.5 Deployment Guide for Application Developers.

Deploying the .NET Framework Client Profile with components hosted locally

The .NET Framework Client Profile is set to automatically download and install its component from the Microsoft Download Center. However, for some users in some cases this may not be possible. In those situations administrator may host the components that make up the .NET Framework Client Profile on their own network.

The following instructions describe how administrators and developers modify and redeploy the .NET Framework Client Profile Web bootstrapper package locally. 

  1. Download the dotnetfx35clientsetup.exe Web bootstrapper and save it to your computer. This package can be obtained at the Microsoft Download Center.

  2. Extract the contents of Web bootstrapper package to a local folder.

    1. Create a folder on your computer, such as C:\NETFXCLIENT

    2. Enter the following command line to extract the contents to your local folder.

      NoteNote:

      See the appendix of this document for more information about the folder layout.

      dotnetfx35clientsetup.exe /x "C:\NETFXCLIENT"

  3. In the DotNetClientFx folder, view the Product.xml file.

    The Product.xml file contains the commands, install conditions, and download locations that will be used to install the .NET Framework Client Profile.

  4. Download the files with the Homesite references and save them to your local Web server.

    1. Use the URL in the HomeSite property to download the packages. At the end of the Product.xml file, there will be a <PackageFiles /> section. Some of the <PackageFile /> sections in <PackageFiles /> contain a HomeSite property.

    2. Save the packages to a Web folder that can be accessed from your network.

  5. In the DotNetClientFx folder, modify the Product.xml file.

    1. Update the HomeSite property in Product.xml file to point to the Web location you created previously.

    2. Save the Product.xml file.

  6. Place all the contents of the NETFXClient folder in a self-extracting executable and configure it to execute "setup.exe" after extracting the contents.

    1. Use any utility program available that can help you create a self-extracting file that will execute a command when done extracting the contents of the file.

    2. Make sure to include all the contents of the C:\NETFXCLIENT folder in your self-extracting file.

    3. The self-extracting executable file should execute "setup.exe".

  7. Place the self-extracting executable on your server for download or deployment.

NoteNote:

The package you just created will not be code signed. When users attempt to browse to the location created by the administrator to install the .NET Framework Client Profile, they will be prompted to confirm the installation and verify the publisher of the file. No publisher will be listed.

Additionally, administrators might want to host localized versions. The following instructions describe how to host the localized versions of the .NET Framework Client Profile.

  1. In the Langpacks folder, view the Product_<language>.xml file for each language you intend to host.

  2. Download the files with the Homesite references and save them to your local Web server.

    1. Use the URL in the HomeSite property to download the packages. At the end of the Product_<language>.xml file, there will be a <PackageFiles /> section. Some of the <PackageFile /> sections in <PackageFiles /> contain a HomeSite property.

    2. Save the packages to a Web folder that will be accessible from your network.

  3. In the DotNetClientFx folder, modify the Product_<language>.xml files.

    1. Update the HomeSite property in Product.xml file to point to the Web location you created previously.

    2. Save the Product_<language>.xml file.

  4. Place all the contents of the NETFXCLIENT folder in a self-extracting executable and configure it to execute "setup.exe" after extracting the contents.

    1. Use any utility program available that can help you create a self-extracting file that will execute a command when done extracting the contents of the file.

    2. Make sure to include all the contents of the C:\NETFXCLIENT folder in your self-extracting file.

    3. The self-extracting executable file should execute "setup.exe"

  5. Place the self-extracting executable on your server for download or deployment.

    Note   The package you just created will not be code signed. When users attempt to browse to the location created by the administrator to install the .NET Framework Client Profile, they will be prompted to confirm the installation and verify the publisher of the file. No publisher will be listed.

NoteNote:

The .NET Framework Client Profile Web bootstrapper will detect the operating system and .NET Framework version installed on the local computer. If the computer does not meet the requirements necessary to install the .NET Framework Client Profile payload, the .NET Framework Client Profile Web bootstrapper will install the latest version of the .NET Framework 3.5. In this scenario, the administrator may also need to host the components of the .NET Framework 3.5. For more information about deploying the .NET Framework 3.5 or later, see .NET Framework 3.5 Deployment Guide for Application Developers.

Deploying the .NET Framework Client Profile using Active Directory

Deploying the .NET Framework Client Profile using Active Directory is currently not supported.

The .NET Framework Client Profile redistributable package is available in two formats:

  • DotNetFx35Client.exe - This is a stand-alone executable file that contains all the components that are required to deploy to the .NET Framework Client Profile or .NET Framework version 3.5 Service Pack 1 on all supported operating systems. This executable does not contain language packs. The .NET Framework Client Profile language packs are available as separate per-language stand-alone executable files. This package can be obtained at the Microsoft Download Center.

  • DotNetFx35ClientSetup.exe - This is a lightweight bootstrapper that downloads required components from the Web during setup. It does not contain any .NET Framework Client Profile components in the package. It will detect, download, and install only required components. The bootstrapper will download and install the language pack that matches the language of the user’s operating system. Standalone language packs can be used to install additional language support. This package can be obtained at the Microsoft Download Center.

You can use either package on all supported operating systems. The bootstrapper will detect the operating system and determine whether the .NET Framework Client Profile or the .NET Framework version 3.5 Service Pack 1 can be installed.

Installation Requirements

This section describes the software and hardware requirements for installing the .NET Framework Client Profile. If the minimum requirements are not met, the .NET Framework setup process stops the installation.

Software Requirements

The .NET Framework Client Profile requires one of the following operating systems on the target computer:

  • Microsoft Windows XP Home or Microsoft Windows XP Professional, both with Service Pack 2 or later.

  • Microsoft Windows Server 2003 family with Service Pack 1 or later.

  • Microsoft Vista.

  • Microsoft Windows Server 2008.

Hardware Requirements

The following table lists the hardware requirements for running the .NET Framework Client Profile.

CPU required

RAM required

Minimum

Pentium 400 MHz

96 MB

Recommended

Pentium 1 GHz or higher

256 MB or more

Where to obtain the .NET Framework Client Profile Redistributable Package

The .NET Framework Client Profile Web redistributable package can be obtained from Microsoft Download Center. The .NET Framework Client Profile "offline" redistributable package can be obtained from the Microsoft Download Center.

In some situations, it might be impractical for you to automatically install the .NET Framework Client Profile with your application. In that case, you can have users install the .NET Framework Client Profile themselves.

However, do not assume that users of your application know where to get the .NET Framework Client Profile or how to install it. In your setup process, provide instructions for how users can locate and install the .NET Framework Client Profile.

Detecting the .NET Framework Client Profile

You can detect whether the .NET Framework Client Profile is already installed by reading a registry key or by querying the user-agent string in Internet Explorer or Firefox.

Reading Registry Keys

The .NET Framework Client Profile installer writes registry keys when installation has finished successfully. You can test whether the .NET Framework Client Profile is installed by checking the registry keys listed in the following table.

Registry key name

Value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\DotNetClient\v3.5

Name: Install

Type: DWORD

Data: 1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\DotNetClient\v3.5

Name: SP

Type: DWORD

Data: 1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\DotNetClient\v3.5

Name: Version

Type: REG_SZ

Data:

3.5.{build}.{revision}

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform

Name: .NET Client 3.5.{build}.{revision}

Type: REG_SZ

Data:

Reading the User-Agent String in a Browser

When the .NET Framework Client Profile is installed on a computer, the .NET Framework Client Profile version number appears as part of the user-agent string that is reported in browser headers. The following example shows a sample page that uses JavaScript to detect and report whether the .NET Framework Client Profile is installed.

<html>
  <head>
    <title>Test for .NET Framework Client Profile</title>
    <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8" />
    <script type="text/JavaScript">
    <!--
    var NETFXClientRuntimeVersion = "3.5.21022";
    
    function body_onload()
    {
      var result = document.getElementById("result");
      if (HasRuntimeVersion(NETFXClientRuntimeVersion))
      {
          result.innerHTML = "This machine has the correct version of the .NET Framework Client Profile runtime: " 
          + NETFXClientRuntimeVersion + "." 
          + "\n\nThis machine's userAgent string is: " 
          + navigator.userAgent + ".";
      } 
      else
      {
        result.innerHTML = "The .NET Framework Client Profile is not installed on this computer.<br/>"
            + "Click <a href='http://msdn.microsoft.com/windowsvista/default.aspx'>"
            + " here</a> to get the .NET Framework Client Profile now.";}
    }
    
    //
    // Retrieve the version from the user agent string and compare with specified version.
    //
    function HasRuntimeVersion(versionToCheck)
    {
      var userAgentString = 
           navigator.userAgent.match(/.NET Client 3.5.[0-9]+/g);
      if (userAgentString != null)
      {
        var i;
        for (i = 0; i < userAgentString.length; ++i)
        {
          if (CompareVersions(GetVersion(versionToCheck), 
                GetVersion(userAgentString[i])) <= 0)
            return true;
        }
      }
      return false;
    }

    //
    // Extract the numeric part of the version string.
    //
    function GetVersion(versionString)
    {
      var numericString = versionString.match(/([0-9]+)\.([0-9]+)\.([0-9]+)/i);
      return numericString.slice(1);
    }

    //
    // Compare the version strings by converting them to numeric format.
    //
    function CompareVersions(version1, version2)
    {
      for (i = 0; i < version1.length; ++i)
      {
        var number1 = new Number(version1[i]);
        var number2 = new Number(version2[i]);

        if (number1 < number2)
          return -1;
        if (number1 > number2)
          return 1;
      }
      return 0;
    }
    
    -->
    </script>
  </head>
  
  <body onload="body_onload();">
    <div id="result" ></div>
  </body>
</html>

If the search for the string ".NET Framework Client Profile" version is successful, the following message is displayed:

This machine has the correct version of the .NET Framework Client Profile runtime: 3.5.28015.00.

This machine's userAgent string is: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET Client 3.5.28015.00).

NoteNote:

The details of the user agent string vary slightly according to the browser and browser version that is being used to test for the .NET Framework Client Profile.

If the .NET Framework Client Profile is not installed, the following message is displayed:

The .NET Framework Client Profile is not installed on this computer.

Click here to get the .NET Framework Client Profile now.

NoteNote:

The .NET Framework Client Profile installer may choose to install the full .NET Framework version 3.5 Service Pack 1 package depending on the operating system and version of the .NET Framework already installed. For more information about detecting the .NET Framework, see .NET Framework 3.5 Deployment Guide for Application Developers.

Command line options for the .NET Framework Client Profile Redistributable Package

The following table lists options that you can specify when you run the .NET Framework Client Profile redistributable installation program from the command line.

Option

Description

/q

Suppresses all UI. An .ini file cannot be specified with this option.

/qb

Never block on user input.

/passive

Never block on user input. (Same as /qb.)

/uninstall

Uninstalls the product.

/norestart

Specifies that the installer does not restart the computer after installation completes. The redistributable installer returns ERROR_SUCCESS_REBOOT_REQUIRED (3010) if a restart is required.

/progress <pipe-name>

Specifies a pipe-name through which events are raised. Intended for use in customized deployment user interfaces.

/?

Displays this list of options.

/x <directory path>

Extracts the contents of the .NET Framework Client Profile package to the directory path specified.

Error Codes for the .NET Framework Client Profile Redistributable Package

The following table lists error codes that can be returned by the .NET Framework Client Profile redistributable installation program. The error codes are the same for all versions of the installer.

Error code

Value

Description

ERROR_SUCCESS

0

The action completed successfully.

ERROR_INSTALL_USEREXIT

1602

User canceled installation.

ERROR_INSTALL_FAILURE

1603

A fatal error occurred during installation.

ERROR_INSTALL_ALREADY_RUNNING

1618

An installation is already in progress.

ERROR_UNKNOWN_PRODUCT

1605

This action is valid only for products that are currently installed.

ERROR_INVALID_COMMAND_LINE

1639

Invalid command-line argument.

ERROR_SUCCESS_REBOOT_INITIATED

1641

The installer has initiated a restart. This indicates success, and setup will continue after restart. (The restart is not performed if the /norestart option was specified.)

ERROR_SUCCESS_REBOOT_REQUIRED

3010

A restart is required to complete the installation. This message indicates success.

ERROR_OUTOFMEMORY

14

Not enough storage is available to complete this operation.

Windows Presentation Foundation applications will not print with the .NET Framework Client Profile

Windows Presentation Foundation (WPF) applications will not print when they are run on .NET Framework Client Profile. The .NET Framework Client Profile does not include the XPS Essentials Pack 1.0 required by WPF to enable printing functionality. When a user attempts to print from a WPF application, the user will be prompted to install the XPS Essentials Pack 1.0 and its prerequisites.

There are two options to work around this issue:

  1. Provide instructions to the user to install MSXML 6.0 and XPS Essentials Pack 1.0 before they run the WPF application that will require printing functionality.

    1. Users should be instructed to download MSXML 6.0.

    2. Users should be instructed to download XPS Essentials Pack 1.0.

  2. Install MSXML 6.0 and XPS Essentials Pack 1.0 with the .NET Framework Client Profile deployment.

    1. Create a folder for the XPS Essentials Pack requirements, such as \XPSEP\

    2. Copy the following XML to a Product.xml file and save the Product.xml file to the XPS Essentials Pack folder, such as \XPSEP\Product.xml.

      <?xml version="1.0" encoding="utf-8" ?>
      
      <Product
        xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
        ProductCode="Microsoft.XPS.Essentials.Pack.1.0">
      
        <Commands>
          <Command PackageFile="msxml6_x86.msi"
            Arguments="REBOOT=ReallySuppress"
            Log="msxml6_x86.log"
            EstimatedInstalledBytes="1500000">
      
            <InstallConditions>
              <FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired" />
            </InstallConditions>
      
            <ExitCodes>
              <ExitCode Value="0" Result="Success"/>
                <ExitCode Value="1605" Result="Success" />
                <ExitCode Value="3010" Result="SuccessReboot" />
                <DefaultExitCode Result="Fail" />
            </ExitCodes>
      
          </Command>
      
          <Command PackageFile="XPSEP XP and Server 2003 32 bit.msi"
            Arguments="REBOOT=ReallySuppress"
            Log="XPSEP_XP_32bit.log"
            EstimatedInstalledBytes="7900000">
      
            <InstallConditions>
              <FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired" />
            </InstallConditions>
      
            <ExitCodes>
              <ExitCode Value="0" Result="Success"/>
                <ExitCode Value="1605" Result="Success" />
                <ExitCode Value="3010" Result="SuccessReboot" />
                <DefaultExitCode Result="Fail" />
            </ExitCodes>
      
          </Command>
        </Commands>
      
        <PackageFiles CopyAllPackageFiles="false">
          <PackageFile Name="msxml6_x86.msi" HomeSite="http://download.microsoft.com/download/e/a/f/eafb8ee7-667d-4e30-bb39-4694b5b3006f/msxml6_x86.msi" PublicKey="-" />
          <PackageFile Name="XPSEP XP and Server 2003 32 bit.msi" HomeSite="http://download.microsoft.com/download/2/5/2/2526f55d-32bc-410f-be18-164ba67ae07d/XPSEP%20XP%20and%20Server%202003%2032%20bit.msi" PublicKey="-" />
        </PackageFiles>
      
      </Product>
      
    3. Create a language folder for the Package.xml file, such as \XPSEP\en

    4. Copy the following XML to a Package.xml file and save the Package.xml file to the XPS Essentials Pack language folder, such as \XPSEP\en\Package.xml.

      <?xml version="1.0" encoding="utf-8" ?>
      
      <Package
        xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
        Name="DisplayName"
        Culture="Culture">
      
        <Strings>
          <String Name="PRODUCT">Microsoft XPS Essentials Pack 1.0</String> <!-- ARP entry -->
      
          <String Name="DisplayName">XPS Essentials Pack 1.0</String>
          <String Name="Culture">en</String>
          <String Name="AdminRequired">Administrator permissions are required to install the XPS Essentials Pack 1.0. Contact your administrator for assistance.</String>
        </Strings>
        
      </Package>
      

Developers and administrators can now deploy the XPS Essentials Pack with their .NET Framework Client Profile deployment. Developers and administrators can follow the instructions in the "Deploying the .NET Framework Client Profile with components hosted locally" section of this document for details on packaging for deployment.

For information about other known installation issues, see the Microsoft .NET Framework Client Profile Release Notes.

The following log files are created during the installation of the .NET Framework Client Profile:

  • Ah_install.log

  • Ah_installUi.log

  • Ah_download.log

Each component included in the deployment of the .NET Framework Client Profile creates its own log, including the following:

  • .NET Framework 2.0 SP2 Client Profile: Ah_fx20.log

  • .NET Framework 3.0 SP2 Client Profile: Ah_fx30.log

  • .NET Framework 3.5 SP1 Client Profile: Ah_fx35.log

  • RGB Rasterizer: Ah_rgb9rast.log

  • WIC: ah_wic_x86.log

For non-English installations, the following log files are also created:

  • Ah_lp<language>20.log

  • Ah_lp<language>30.log

  • Ah_lp<language>35.log

During the .NET Framework 3.5 setup process, the log files are located in the %temp% directory. A customized application deployment that uses the .NET Framework Client Profile will also log its setup output to the %temp% directory.

Windows Installer Error Codes

For a list of error codes, see the Windows Installer Error Codes page on the MSDN Web site.

The following table lists the components in the .NET Framework Client Profile.

Path

Filename

Web Package

Offline Package

Description

(Root Folder)

Setup.exe

Yes

Yes

Setup bootstrapper.

ClickOnceInstaller.exe

Yes

Yes

ClickOnce bootstrapper.

ClickOnceInstaller.exe.config

Yes

Yes

ClickOnce bootstrapper configuration file.

Deployment.xml

Yes

Yes

Deployment configuration file.

Setupres.<languageCode>.dll

Yes

Yes

Language resources files. There is one for every language supported.

Setupres.dll

Yes

Yes

English string resources.

Dotnetfxclient20_x86.exe

No

Yes

.NET Framework Client Profile 2.0 components.

DotNetFxClient30_x86.exe

No

Yes

.NET Framework Client Profile 3.0 components.

DotNetFxClient35_x86.dll

No

Yes

.NET Framework Client Profile 3.5 components.

RGB9RAST_x86.msi

No

Yes

WIC_x86_ENU.exe

No

Yes

Images

Bground10.jpg

Yes

Yes

Background image for default installer.

Bground_rtl.jpg

Yes

Yes

Background image for default installer in right to left languages.

DotNetClientFx

Product.xml

Yes

Yes

XML file that describes the installation instructions for the product to be installed.

DotNetClientFx \ (Language folders)

Package.xml

Yes

Yes

XML file that contains the localized strings for the product to be installed.

Langpacks

Product_<language>.xml

Yes

No

XML file that describes the installation instructions for the localized product resources to be installed.

Langpacks \ (Language folders)

Package.xml

Yes

No

XML file that contains the localized strings for the product to be installed.

Date

History

Reason

August 2008

Added topic.

Information enhancement.

Community Additions

ADD
Show:
© 2014 Microsoft