.NET Framework Client Profile Deployment Guide

Contents

1       Introduction to the Client Profile. 2

1.1         .NET Framework Client Profile. 2

1.1.1          Client Profile Redistributable Packages. 2

1.1.2          Client Profile deployment boot strapper. 3

1.2         .NET Framework Client Profile Deployment Scenarios. 4

2       For Administrators. 5

2.1         Deploying the Client Profile. 5

2.2         Deploying the Client Profile with components hosted locally. 6

2.3         Deploying Client Profile using Active Directory. 7

3       For Application Developers. 8

3.1         Installation Requirements. 8

3.2         Where to obtain the .NET Framework Client Profile Redistributable Package. 9

3.3         Detecting the .NET Framework Client Profile. 9

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

3.5         Error Codes for .NET Framework Client Profile Redistributable Package. 13

4       Known Installation Issues. 14

5       Troubleshooting. 16

6       Appendix. 17

 

 

NOTE: The software referenced in this document, including without limitation, the .NET Framework Client Profile, .NET Framework 3.5, .NET Framework 3.5 Service Pack 1, 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.

 

1         Introduction to the Client Profile

The .NET Framework Client Profile (Client Profile) was created to answer the feedback from many customers that a smaller framework was needed specifically for Client Applications. The Client Profile is a subset of assemblies already contained within .NET Framework 3.5 Service Pack 1. The Client Profile subset is focused on fulfilling the needs of Client applications.

The Client Profile contains the following features:

·         Smaller framework deployment - ~28 MB client deployment package

·         Smaller, faster client deployment boot strapper

·         Client Application focused feature set:

o   Common Language Runtime (CLR)

o   ClickOnce

o   Windows Forms

o   Windows Presentation Foundation

o   Windows Communication Foundation

·         Visual Studio 2008 SP1 Integration – Applications can be targeted specifically for the Client Framework subset.

1.1       .NET Framework Client Profile

The Client Profile is made up of a combination of features. The first part is client redistributable packages that are installed by end-users. The second part is the client deployment boot strapper that manages the deployment of redistributable packages.

1.1.1       Client Profile Redistributable Packages

There are no new features specific to the Client Profile. The subset of assemblies is the same as in the full installation of the .NET Framework. The Client Profile is deployed and installed in much the same way that the full .NET Framework is deployed and installed.

Figure 1. Client Framework

As you can see in Figure 1, the .NET Framework is a set of versioned layers that are dependent on the layer below it. The Client Profile is broken down in the same way to ensure that the functional parity would be maintained in the client framework.

The 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.

1.1.1       Client Profile deployment boot strapper

The Client Deployment boot strapper is the part of the Client Profile that manages the deployment of the client redistributable packages. The Client Profile boot strapper is small, approximately 200 KB in size, and is primarily designed to accommodate web based deployment scenarios. The Client Profile boot strapper is also XML file driven to allow for more flexibility of deployment configurations.

Figure 2. Client Profile Bootstrapper

As seen in Figure 2, the Client Profile boot strapper contains several XML files that determine how packages are deployed.

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 and/or uninstalled.

The Product.xml file(s) contains the information needed 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.

1.2       .NET Framework Client Profile Deployment Scenarios

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

Microsoft Windows XP SP2 or greater and Windows Server 2003 do not have any framework components installed by default. The Client Profile redistributable package can be installed on Windows XP. The Client Profile redistributable package will not be installed on Windows Server 2003 as this platform is not intended for use as a client application platform. The following table explains how each platform will be managed to ensure Client Applications are fully functional upon deployment.

As is illustrated in the preceding table, the Client Profile deployment is focused on Windows XP SP2+ with No 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 have the same look, feel and consistency.

NOTE: .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.

2         For Administrators

2.1       Deploying the Client Profile

The intent of the .NET Framework Client Profile is such that application developers can distribute the Client Profile with their application deployments. Application developers are able to 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 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 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 Client Profile payload, the full .NET Framework 3.5 Service Pack 1 will be installed.

NOTE: 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 3.5 Service Pack 1 or later.

NOTE: 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 3.5 Service Pack 1. Administrators are able to work around this issue by installing .NET Framework 3.5 Service Pack 1 instead of the older version of the .NET Framework.

For more information on deploying the .NET Framework 3.5 or later, please refer to the .NET Framework 3.5 Deployment Guide for Application Developers.

2.2       Deploying the 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 situations 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 will allow administrators and developers to modify and redeploy the .NET Framework Client Profile web bootstrapper package.

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.

a.       Create a folder on your computer, ie. C:\NETFXCLIENT

b.  Enter the following command line to extract the contents to your local folder. (Please refer to the appendix of this document for more information on the folder layout.)

dotnetfx35clientsetup.exe /x “C:\NETFXCLIENT”

3.       Go to the DotNetClientFx folder and view the Product.xml file.

a.       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.

a.       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. Use the URL in the HomeSite property to download the packages.

b.      Save the packages to a web folder that will be accessible from your network.

5.       Go to the DotNetClientFx folder and modify the Product.xml file.

a.       Update the “HomeSite” property in Product.xml file to point to the web location you created previously.

b.      Save the Product.xml file.

6.       Place all the contents of the NETFXClient folder in a self-extracting executable and have it execute “setup.exe”.

a.       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.

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

c.       The self-extracting executable file should execute “setup.exe”

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

NOTE: The package you just created will not be Codesigned. 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 if administrators need to host the localized versions of the Client Profile, please modify the following:

1.       Go to the Langpacks folder and view the Product_<language>.xml file for each language you intend on hosting.

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

a.       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. Use the URL in the HomeSite property to download the packages.

b.      Save the packages to a web folder that will be accessible from your network.

3.       Go to the DotNetClientFx folder and modify the Product_<language>.xml files.

a.       Update the “HomeSite” property in Product.xml file to point to the web location you created previously.

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

4.       Place all the contents of the NETFXCLIENT folder in a self-extracting executable and have it execute “setup.exe”.

a.       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.

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

c.       The self-extracting executable file should execute “setup.exe”

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

NOTE: The package you just created will not be Codesigned. 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.

 

NOTE:  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 needed to install the .NET Framework Client Profile payload, the 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 on deploying the .NET Framework 3.5 or later, please refer to the .NET Framework 3.5 Deployment Guide for Application Developers.

2.3       Deploying Client Profile using Active Directory

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

3         For Application Developers

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

DotNetFx35Client.exe - This is a standalone executable file that contains all the components that are required to deploy to the .NET Framework Client Profile or .NET Framework 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 if the .NET Framework Client Profile or the .NET Framework 3.5 Service Pack 1 can be installed.

3.1       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.

NOTE: The .NET Framework Client Profile is targeted for Windows XP computers with no .NET Framework components installed. If the .NET Framework Client Profile installation process detects any other operating system version or any version of .NET Framework installed, the Client Profile installer will install .NET Framework 3.5 Service Pack 1.

Hardware Requirements

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

 

CPU required

RAM required

Minimum

Pentium 400 MHz

96 MB

Recommended

Pentium 1 GHz or higher

256 MB or more

 

3.2       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 web site here. The .NET Framework Client Profile “offline” redistributable package can be obtained from the Microsoft Download Center here.

In some situations, it might be impractical for you to automatically install the .NET Framework 3.5 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.

3.3       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 3.5 installer writes registry keys when installation has finished successfully. You can test whether.NET Framework 3.5 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: 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).

(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.

NOTE: The .NET Framework Client Profile installer may choose to install the full .NET Framework 3.5 Service Pack 1 package depending on the operating system and version of the .NET Framework already installed. Please refer to the .NET Framework 3.5 Deployment Guide for Application Developers for additional information in detecting the .NET Framework.

3.4       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 3.5 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 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 reboot 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.

 

3.5       Error Codes for .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 reboot 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.

 

4         Known Installation Issues

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

Windows Presentation Foundation applications will not print when run on .NET Framework Client Profile. The .NET Framework Client Profile does not include the XPS Essentials Pack 1.0 required by Windows Presentation Foundation to enable printing functionality. When a user attempts to print from a Windows Presentation Foundation 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 running the WPF application that will require printing functionality.

a.       Users should be instructed to download MSXML 6.0 from this location.

b.      Users should be instructed to download XPS Essentials Pack 1.0 from this location.

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

a.       Create a folder for the XPS Essentials Pack requirements, ie. \XPSEP\

b.      Copy the following to a Product.xml file and save the Product.xml file to the XPS Essentials Pack folder, ie. \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>

 

c.       Create a language folder for the Package.xml file, ie. \XPSEP\en

d.      Copy the following to a Package.xml file and save the Package.xml file to the XPS Essentials Pack language folder, ie. \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 Client Profile deployment. Developers and administrators can follow the instructions in the Deploying the 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.

5         Troubleshooting

The following log files are created during the installation of the 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 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.

6         Appendix

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 describing the installation instructions for the product to be installed.

DotNetClientFx \ (Language folders)

Package.xml

Yes

Yes

XML file containing the localized strings for the product to be installed.

Langpacks

Product_<language>.xml

Yes

No

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

Langpacks \ (Language folders)

Package.xml

Yes

No

XML file containing the localized strings for the product to be installed.