Export (0) Print
Expand All

Installing Microsoft .NET Framework 3.0 on Windows XP Embedded Service Pack 2

4/25/2007

Microsoft Corporation.

February 2007.

Learn what's needed to run the .NET Framework 3.0 desktop installer on a Microsoft® Windows XP Embedded Service Pack 2 image. Also, learn how to deploy some .NET 3.0 applications on those run-time images.

Windows XP Embedded Service Pack 2 systems.

To include the .NET Framework 3.0 in Windows XP Embedded Service Pack 2 systems, first construct a run-time image that is compatible with .NET Framework 3.0. Next, run the .NET Framework 3.0 desktop installation package for Windows XP Professional on that image after First Boot Agent (FBA) is finished.

.NET Framework 3.0 consists of new technologies including Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace (WCS).

Let's look at what's required for the .NET Framework 3.0 desktop installation on Service Pack 2 in more detail.

The following components are required to successfully execute the .NET Framework 3.0 desktop installation package on a run-time image built with the Windows XP Embedded Service Pack 2:

  • Accessibility Core
  • Active Directory Service Interface (ADSI) Core
  • Base Performance Counters
  • COM+ Services
  • Common Control Libraries Version 5
  • Common File Dialogs
  • Distributed Transaction Coordinator (MSDTC)
  • Down-level Shell Compat
  • GDI+ XP
  • HTML Help Engine
  • Internet Explorer
  • Local Security Authority Subsystem (LSASS)
  • Message Queuing (MSMQ) Core
  • Microsoft Data Access Components (MDAC)
  • Microsoft Management Console (MMC)
  • Microsoft Visual C++ Run Time
  • Microsoft-Windows-HTTP
  • Ole Automation
  • OLE Dialog Interfaces
  • Performance Counter Configuration
  • Performance Data Helper
  • Primitive: Cabinet
  • Primitive: Crypt32
  • Primitive: CryptUI
  • Primitive: Dbgeng
  • Primitive: Dbghelp
  • Primitive: Imagehlp
  • Primitive: Imm32
  • Primitive: Mpr
  • Primitive: Msi
  • Primitive: Msimg32
  • Primitive: Mswsock
  • Primitive: Netapi32
  • Primitive: Ntdll
  • Primitive: Ole32
  • Primitive: Oleaut32
  • Primitive: Psapi
  • Primitive: Secur32
  • Primitive: Security
  • Primitive: Setupapi
  • Primitive: Shell32
  • Primitive: Shlwapi
  • Primitive: Userenv
  • Primitive: uxtheme
  • Primitive: Version
  • Primitive: Winmm
  • Primitive: Winspool
  • Primitive: Wintrust
  • Primitive: Ws2_32
  • Primitive: Wsock32
  • Primitive: Wtsapi32
  • Registry Editor
  • Remote Registry Service
  • Rich Edit Control Version 3.0
  • RPC Local Support
  • System Restore Core
  • Urlmon Library
  • Video For Windows Core
  • Windows API – Advanced
  • Windows API – GDI
  • Windows API – Kernel
  • Windows API – User
  • Windows Installer Service
  • Windows Logon
  • Wininet Library
  • WMI Core
  • WMI Tools
  • WMI Win32 Provider

Include all of these components in a new .NET Framework 3.0 macro component and build your Service Pack 2 run-time image with that new macro component.

In addition to the components required for the .NET Framework 3.0 installation, other components are needed in the Service Pack 2 run-time image for the system to support certain .NET technologies and applications.

WPF

WPF depends on DirectX 9.0. Add the following components to the .NET Framework 3.0 macro component to support the rich functionality of WPF:

  • DirectX 9.0c
WCF

Internet Information Services (IIS) must be present to host a WCF service in IIS. Add the following components to the .NET Framework 3.0 macro component to enable Web host script mappings:

  • IIS Web Server
Applications Using Rich Features of WPF, WCF, WF, and WCS

Deploying applications using the rich features of these .NET Framework 3.0 technologies may require including additional components in the .NET Framework 3.0 macro component, such as:

  • Internet Explorer 7
  • WMP 10
  • MSMQ

A macro component is a component that has dependencies on other components and has no file or registry resources of its own. Macro components are useful for bundling components that must appear together in a configuration, or for bundling functionality that will be used again. Instead of adding the individual components to the configuration, you create a macro component that has dependencies on all of them and then you add the single macro component to the configuration.

To create and include a .NET Framework 3.0 macro component

  1. Use Component Designer to create a new .NET Framework 3.0 macro component. For more information on creating a component in Component Designer, see Component Authoring at this Microsoft Web site.
  2. Make the .NET Framework 3.0 macro component dependent on the components that are specified in the preceding section Components Required for .NET Framework 3.0 Installation.
  3. Import the resulting .sld file for the .NET Framework 3.0 macro component into your database, as with any other component.
  4. Use Target Designer to include the .NET Framework 3.0 macro component in your Windows XP Embedded Service Pack 2 run-time image.

After building the Windows XP Embedded Service Pack 2 run-time image with the new .NET Framework 3.0 macro component and after FBA has finished, download and run the .NET Framework 3.0 desktop installer.

The desktop installer is available in two versions:

  • dotnetfx3.exe, a 53 MB full install package
  • dotnetfx3setup.exe, a 3 MB Web install package

The Web install package downloads installers for only those components not already present in the Service Pack 2 run-time image. For example, if the .NET Framework 2.0 component is included in the run-time image, the Web install package does not download the .NET Framework 2.0 installer.

In contrast, the full desktop installer includes installers for all required components.

Bb417255.note(en-US,WinEmbedded.5).gifNote:
When using the Web install version of the .NET Framework 3.0 desktop installer, the Background Intelligent Transfer Service (BITS 2.0) component must be added the set of components included in the .NET Framework macro component. For more information on creating the .NET Framework macro component, see Creating a Macro Component. Furthermore, the Service Pack 2 run-time image must have Internet access to use the Web install package.

Approximately 500 MB of free disk space is required to install .NET Framework 3.0.

To download and run the .NET Framework 3.0 desktop installer

  1. Download the NET Framework 3.0 desktop installation package for XP-Pro from the Mobile and Embedded Communications Extranet (ECE) site.
    Bb417255.note(en-US,WinEmbedded.5).gifNote:
    Windows XP Embedded software used in commercial products must be downloaded from the ECE site.
  2. Copy the installer to your Service Pack 2 run-time image.
  3. Run one of the following commands from within the Service Pack 2 run-time image after FBA is finished:
    dotnetfx3.exe /Q
    
    for the full install package, or
    dotnetfx3setup.exe /Q
    
    for the Web install package.
    It is very important to use the /Q command-line switch when invoking the installer. This switch selects no UI; therefore, run the command from a batch file that indicates when the installation is completed.

After running the .NET Framework 3.0 installer, install language packs if necessary.

To install .NET Framework 3.0 language packs

  1. Download the language packs from this Microsoft Web site.
  2. Run the language packs after successfully installing the.NET Framework 3.0 on Windows XP Embedded Service Pack 2 run-time image.
Bb417255.note(en-US,WinEmbedded.5).gifNote:
The .NET Framework 3.0 Web install package detects any Multilingual User Interface (MUI) language packs installed on the Service Pack 2 run-time image and automatically installs the corresponding language packs for .NET Framework 3.0.

The procedures and information provided in this white paper instruct the reader in preparing a Windows XP Embedded Service Pack 2 run-time image for running the .NET Framework 3.0 desktop installer.

Show:
© 2014 Microsoft