Microsoft .NET Framework 3.5 Client Profile Readme

 

Contents

1.      System Requirements. 1

1.1.       Supported Architectures. 1

1.2.       Supported Operating Systems. 1

1.3.       Hardware Requirements. 2

1.4.       Installation of .NET Framework 3.5 SP1. 2

2.      Known Issues. 2

2.1.       Installing. 2

2.2.       Uninstalling. 3

2.3.       Product Issues. 3

2.3.1.         General Issues. 3

2.3.2.         Unsupported Assemblies. 4

2.3.3.         Unsupported APIs. 5

 

 

1.                 System Requirements

1.1.          Supported Architectures

·         X86

1.2.          Supported Operating Systems

·         Microsoft Windows XP SP2 or greater

1.3.          Hardware Requirements

·         Minimum: 400 MHz CPU, 96 MB RAM, 800x600 256-color display

·         Recommended:  1.0 GHz or higher CPU, 256 MB or more RAM, 1024x768 high-color 32-bit display

·         Up to 500 MB of hard disk space may be required 

1.4.          Installation of .NET Framework 3.5 SP1

The .NET Framework 3.5 Client Profile is not intended to install on all platforms supported by the .NET Framework. The .NET Framework 3.5 Client Profile will only install to Windows XP SP2 or greater when no versions of the .NET Framework are detected on the computer. The .NET Framework 3.5 Client Profile will switch and install full .NET Framework 3.5 SP1 when any other combination of Operating System and .NET Framework versions are detected on the computer. Please refer to the .NET Framework 3.5 Client Profile Deployment Guide for more information.

2.                 Known Issues

2.1.          Installing

2.1.1.     Uninstall earlier pre-release versions of .NET Framework 3.5 Client Profile prior to installing the released version.

If you have installed earlier pre-release versions of .NET Framework 3.5 Client Profile, then you must uninstall them prior to running this installation by using Add or Remove Programs.

To resolve this issue:

There is no workaround available.

2.1.2.     Windows XP computers with .NET Framework 3.5 Client Profile cannot be upgraded to Windows Vista until .NET Framework 3.5 Client Profile is uninstalled.

If you have installed the .NET Framework 3.5 Client Profile on your Windows XP computer then attempt to upgrade to Windows Vista, you will be prompted to uninstall the .NET Framework 3.5 Client Profile before proceeding with the upgrade.

User must uninstall .NET Framework 3.5 Client Profile prior to upgrading your Windows XP computer to Windows Vista. After the computer is upgraded to Windows Vista, .NET Framework 3.5 Client Profile applications may not function properly. Users can install .NET Framework 3.5 SP1 after upgrading to Windows Vista.

To resolve this issue:

Users must uninstall .NET Framework 3.5 Client Profile before upgrading to Windows Vista. After the upgrade to Windows Vista, users can install .NET Framework 3.5 SP1. For more details, please see KB955459.

2.2.          Uninstalling

There are no known uninstall issues with .NET Framework 3.5 Client Profile. For any additional issues with .NET Framework 3.5 SP1, please see the .NET Framework 3.5 SP1 Readme.

2.3.          Product Issues

2.3.1.     General Issues

2.3.1.1.                        Windows Presentation Foundation applications will not print when using .NET Framework 3.5 Client Profile

Applications that use the printing functionality of Windows Presentation Foundation will not function. The application end-user will be prompted to install the XPS Essentials Pack 1.0 to enable Windows Presentation Foundation printing.

The .NET Framework 3.5 Client Profile does not include the latest versions of MSXML 6.0 and XPS Essentials Pack 1.0. However, developers can include this functionality in their application deployments. For more information, please see the .NET Framework 3.5 Client Profile Deployment Guide.

To resolve this issue:

Users must install MSXML 6.0 and XPS Essentials Pack 1.0 to enable full printing functionality in Windows Presentation Foundation applications. For more details, please see KB955465.

2.3.1.2.                        .NET Framework 3.5 applications may be prompted to upgrade to the full installation of .NET Framework 3.5 SP1

Existing .NET Framework applications may not execute properly when run using .NET Framework 3.5 Client Profile. The .NET Framework 3.5 Client Profile requires that all applications have a corresponding configuration file that declares the application is a client application. If the application does not have the appropriate entry in their configuration file, end-users will be prompted to install .NET Framework 3.5 SP1.

To resolve this issue:

To resolve this issue, one of the following actions may be taken.

1.                   Application developers may add a configuration file with the following entry to their application.

<configuration>
   <startup>
      <supportedRuntime version="v2.0.50727" sku=”client” />
   </startup>
</configuration>


2.                   Application developers may develop their applications in Visual Studio 2008 SP1 and use the advanced compile options to set the application to target the Client Framework.

3.                   End-user users may choose to upgrade to .NET Framework 3.5 SP1 to use the application.

2.3.1.3.                        .NET Framework applications that enumerate the ADO.NET Data Providers will get positive confirmation that the Oracle data provider is installed when it is not

The .NET Framework machine.config file contains references to the ADO.NET Oracle Data Provider. However, the file, System.Data.OracleClient.dll, is not included in .NET Framework 3.5 Client Profile. Any application that attempts to enumerate the ADO.NET Data Providers will receive positive confirmation that the Oracle Data Provider is installed and available, however, it is not.

To resolve this issue:

Application developers that do require the ADO.NET Oracle Data Providers for their applications will need to install .NET Framework 3.5 SP1.

2.3.1.4.                        Windows Communications Foundation services cannot be monitored or controlled when using the .NET Framework 3.5 Client Profile

Applications that allow user to monitor Windows Communications Foundation services will not function. The Windows Management Instrumentation that allows for the monitoring and control of Windows Communications Foundation services is not included in the .NET Framework 3.5 Client Profile. If the application requires this functionality, then developers or users will need to install .NET Framework 3.5 SP1.

To resolve this issue:

There is no workaround for this issue. Users or developers will need to install .NET Framework 3.5 SP1.

2.3.1.5.                        Applications that attempt to install any older versions of .NET Framework will prompt users to install .NET Framework 3.5 SP1 or greater

The .NET Framework 3.5 Client Profile is not supported with any older versions of the .NET Framework. Older applications that attempt to install an older version of .NET Framework will display a prompt informing users that the version of the .NET Framework that is being installed is not compatible with the .NET Framework 3.5 Client Profile. In addition, any quiet mode installation of older version of the .NET Framework will also prompt the user to install the latest version of the .NET Framework.

To resolve this issue:

Users will need to stop the installation of the application that is installing the older version of the .NET Framework. Users can then install .NET Framework 3.5 SP1 or greater. After the installation is done, users can then restart the application installation that was previously blocked. The application installation should be able to detect that a new version of the .NET Framework is installed and continue with the installation of their application.

2.3.2.     Unsupported Assemblies

The following assemblies are included as infrastructure to support the .NET Framework 3.5  Client Profile but cannot be used directly by your application.  Directly referencing and using these assemblies by an application targeting the Client Profile is unsupported.  These assemblies may be removed in future versions of the Client Profile.

·         csc.exe

·         jsc.exe

·         Microsoft.JScript.dll

·         Microsoft.Vsa.dll

·         System.Messaging.dll

2.3.3.     Unsupported APIs

The following APIs are not supported on the .NET Framework 3.5 Client Profile.  Do not use them in an application that targets the Client Profile.  These APIs may be removed in future versions of the .NET Framework Client Profile.

System.dll

·         System.CodeDom.* (all APIs in this namespace)

·         System.CodeDom.Compiler.* (all APIs in this namespace)

o   Except GeneratedCodeAttribute

·         Microsoft.VisualBasic.VBCodeProvider

·         Microsoft.CSharp.CSharpCodeProvider

System.Management.dll

·         System.Management.ManagementClass.GetStronglyTypedClassCode(Boolean, Boolean)

·         System.Management.ManagementClass.GetStronglyTypedClassCode(CodeLanguage, String, String)

·         System.Management.Instrumentation.* (all APIs in this namespace)

System.Runtime.Remoting.dll

·         System.Runtime.Remoting.Channels.Http.HttpRemotingHandler

·         System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory

·         System.Runtime.Remoting.Services.RemotingService

System.ServiceModel.dll

·         System.ServiceModel.Activation.* (all APIs in this namespace)

System.ServiceModel.Web.dll

·         System.ServiceModel.Activation.* (all APIs in this namespace)

System.IdentityModel.dll

·         System.IdentityModel.Selectors.* (all APIs in this namespace)

System.Web.Services.dll

·         System.Web.Services.* (all APIs in this namespace)

·         System.Web.Services.Configuration.* (all APIs in this namespace)

·         System.Web.Services.Diagnostics.* (all APIs in this namespace)

·         System.Web.Services.Discovery.* (all APIs in this namespace)

·         System.Web.Services.Protocols.* (all APIs in this namespace)