Note For best results, install on a computer that has not had pre-release versions of .NET Framework 3.0 (formerly WinFX) runtime Components 3.0 installed on it. If your computer has a pre-release version on it, you must remove it in the correct order to ensure a clean uninstall. Follow these Uninstall Instructions to uninstall the pre-release bits before installing this build.
Contents
- System Requirements for Installing .NET Framework 3.0 (formerly WinFX) Runtime Components
- .NET Framework 3.0 (formerly WinFX) Runtime Components: Installation Known Issues
- Troubleshooting Steps for Download Errors
- Windows Communication Foundation Known Issues
- Windows Workflow Foundation Known Issues
1. System Requirements for Installing .NET Framework 3.0 (formerly WinFX) Runtime Components
| Processor | Minimum: - 400 megahertz (MHz) Pentium processor
Recommended: - 1 gigahertz (GHz) Pentium processor
|
| Operating System | .NET Framework 3.0 (formerly WinFX) Runtime Components 3.0 Beta 2 can be installed on any of the following systems: - Microsoft Windows 2003 Server Service Pack 1 (SP1)
- Windows XP SP2
- Windows Vista Beta 2
Installation of .NET Framework 3.0 (formerly WinFX) Runtime Components Beta 2 on the Intel Itanium (IA64) is not supported. |
| RAM | Minimum: Recommended: |
| Hard Disk | Up to 500 MB of available space may be required. |
| CD or DVD Drive | Not required. |
| Display | Minimum: Recommended: - 1024 x 768 high color, 32-bit
|
| Mouse | Not required |
Performance improvement
Performance improvements have not been tuned for minimum system configurations. Increasing your RAM above the recommended system configuration will increase your performance, specifically when running multiple applications, working with large projects, or doing enterprise-level development.
Installation drive
When you start the .NET Framework 3.0 (formerly WinFX) Runtime Components installer, the default installation location is on your system drive, which is the drive that boots your system. Please ensure that the required amount of space is available on your system drive.
2. .NET Framework 3.0 (formerly WinFX) Runtime Components: Installation Known Issues
2.1 Download failure when downloading and installing .NET Framework 3.0 (formerly WinFX) Runtime Components Beta 2.
The download and installation of a .NET Framework 3.0 (formerly WinFX) Runtime Components 3.0 Beta 2 intermittently fails.
To resolve this issue
Rerun .NET Framework 3.0 (formerly WinFX) setup.exe from the Web site and try the download again. See Troubleshooting Steps for Download Errors for more troubleshooting information about download errors.
2.2 Antivirus applications that are configured to clean the Temp folder will cause setup to fail if setup needs to reboot.
If setup needs to reboot, and the antivirus application is set to clean the Temp directory on launch, necessary setup files will be deleted and setup will fail with a program-not-found error.
To resolve this issue
Before running .NET Framework 3.0 (formerly WinFX) Runtime Components setup, change your antivirus applications configuration to not clean the Temp folder on launch or reboot. Consult your antivirus documentation for the steps to accomplish this.
2.3 Launching Maintenance Mode from Add or Remove Programs can take several minutes and might give the appearance that setup has failed.
If you have other processes running when you launch Maintenance Mode, such as virus-scanning software, these processes can slow setup considerably and give the appearance that setup has failed.
To resolve this issue
Be patient. There is no workaround. Setup has not failed.
2.4 No entries are visible in Add Remove Programs to repair / uninstall .NET Framework 3.0 (formerly WinFX) 3.0 on Windows Vista.
You will not see any entries for .NET Framework 3.0 (formerly WinFX) Runtime 3.0 in Add/Remove Programs on Windows Vista .NET Framework 3.0 (formerly WinFX) is an optional Windows feature in Vista.
To resolve this issue
- Click on Start, Control Panel
- On the Control panel Home view, click on Programs
- Select the Turn on or off Windows features under the Installed Programs section
- .NET Framework 3.0 (formerly WinFX) 3.0 is listed as 'Windows Foundation Components for .NET Framework 3.0 (formerly WinFX) 3.0 in the Windows Features dialog
- Toggle the checkbox to install or uninstall
2.5 No Add Remove Programs entry to uninstall Windows Workflow Foundation.
You may get the "Please uninstall Windows Workflow Foundation" error when installing .NET Framework 3.0 (formerly WinFX) Runtime Components Beta 2, but there is no ARP entry for Windows Workflow Foundation to uninstall the product.
To resolve this issue
Download the standalone Microsoft Workflow Foundation MSI and run it to uninstall Windows Workflow Foundation. Download locations:
– or –
For x86 platforms: Run msiexec.exe /x {5ED7CECD-723B-4D61-9FAE-98422084E0C1} in the command-line window to remove Windows Workflow Foundation.
For x64 platforms: Run msiexec.exe /x {8880394F-123C-4920-AC98-EC221D134172} in the command-line window to remove Windows Workflow Foundation.
For ia64 platforms: Run msiexec.exe /x {5E3C4A6B-EB50-4724-AF66-E1D89BCCF245} in the command-line window to remove Windows Workflow Foundation.
2.6 .NET Framework 3.0 (formerly WinFX) installation may overwrite the localized version of MSXML6
On Windows XP SP2 and Windows 2003 SP1, if you have a localized version of MSXML6 previously installed, .NET Framework 3.0 (formerly WinFX) installation will overwrite the localized MXSML6 with the English version.
To resolve this issue
Reinstall the localized version of MSXML6 after installing .NET Framework 3.0 (formerly WinFX).
2.7 .NET Framework 3.0 (formerly WinFX) Beta 2 installation fails on a system with .NET Framework 3.0 (formerly WinFX) Jan CTP or earlier previously installed
.NET Framework 3.0 (formerly WinFX) installation fails with this error:
ERROR_INSTALL_FAILURE 1603 Fatal error during installation
And in one of the %temp%\dd_wcf_retCA*.txt log files, it shows the following:
ServiceModelReg [15:48:08:041]: Installing: Microsoft Digital Identity Service (idsvc)
ServiceModelReg [15:48:08:073]: Error: System.ComponentModel.Win32Exception: The name is already in use as either a service name or a service display name
To resolve this issue
- Open a commnd prompt
- Click: Start
- All Programs
- Accessories
- Command Prompt
- In the command prompt, type: sc delete “InfoCard Service"
- Restart the .NET Framework 3.0 (formerly WinFX) Beta 2 installation
2.8 Cannot re-install .NET Framework 3.0 (formerly WinFX) language packs after uninstalling .NET Framework 3.0 (formerly WinFX) from Vista or from a Windows XP SP2 or Windows 2003 SP1 machine with multiple language packs installed
The installation of .NET Framework 3.0 (formerly WinFX) success but no language packs files are installed.
To resolve this issue
Use the .NET Framework 3.0 (formerly WinFX) uninstall tool to clean up the previous .NET Framework 3.0 (formerly WinFX) installation before re-installing.
3. Troubleshooting Steps for Download Errors
3.1 Background Intelligent Transfer Service (BITS) disabled
This error occurs when the BITS service is disabled, does not exist, has been deleted from the services application, was stopped while download was in progress, or if any service that BITS depends on failed or was deleted. The error message for this problem is "BITS service must be enabled before you start the installation process. Enable the BITS service and run setup again."
To resolve this issue
- On the Start menu, click Run.
- In the Run Dialog box, type services.msc and then click OK.
- In the list of services, right-click Background Intelligent Transfer Service, and then click Properties.
Note: If you do not see Background Intelligent Transfer Service in the list, the service is not installed on your computer. You can download and install BITS from the Microsoft Download Center.
- In the Startup type list, select Manual and then click OK.
If these steps do not resolve the problem, you may need to enable the services that BITS depends on.
To enable dependencies
- Follow steps 1-3 listed above.
- In the Background Intelligent Transfer Service Properties dialog box, click the Dependencies tab.
- For each service listed under This service depends on the following system components, follow steps 3 and 4 listed above to enable the service.
3.2 Configuration Errors
These errors occur when BITS interfaces are not registered or the registry settings are corrupted.
To resolve this issue
Upgrade to BITS 2.0 from the Microsoft Download Center.
– or –
Repair the BITS service by running the bitsadmin tool from the command prompt:
Bitsadmin /util /repairservice /force
You can download the Bitsadmin tool from the Microsoft Download Center.
3.3 .NET work Errors
These errors can occur for one or more of the following reasons:
- Unable to reach download server
- URL not found on the server
- Server is overloaded
- Bad gateway or proxy
- .NET work is disconnected
- Proxy does not support HTTP 1.1
To resolve this issue
Provide correct settings for the proxy server and ensure that your machine is able to correctly resolve the proxy server.
– or –
Upgrade to BITS 2.0. You can download BITS 2.0 from the
Microsoft Download Center.
Note To resolve these errors, exit setup, verify that you are connected to the .NET work, and launch setup again.
3.4 Disk Errors
These errors occur when the BITS service failed to create or write to a file. Another program, such as chkdsk.exe, might be running and may have locked the disk and prevented BITS from writing to the file.
To resolve this issue
Make sure that no other program (for example, chkdsk.exe) that could lock the disk is running and retry the download.
– or –
Restart your computer and then launch setup again. Make sure that you are connected to the Inter.NET .
3.5 Proxy Errors
The BITS service failed because of one of the following proxy-related errors:
- The proxy settings are not valid.
- The proxy server requires authentication.
- The computer is not able to resolve the proxy server.
To resolve this issue
Provide correct credentials for the proxy server authentication and restart setup again.
– or –
Upgrade the proxy server to support HTTP 1.1 and ensure that the proxy supports implicit credentials (like NTLM). You may need to contact your .NET work administrator.
– or –
Bypass the proxy by changing your Inter.NET Explorer proxy settings.
To bypass a proxy server:
- In Inter.NET Explorer, click Tools and then click Inter.NET Options.
- Click the Connections tab and then click LAN Settings.
- Under Proxy server, unselect Use a proxy server for your LAN (these settings will not apply to dial-up or VPN connections) and then click OK.
- Click OK again.
If you need further assistance with your proxy server settings, contact your .NET work administrator.
3.6 Other Errors
The BITS service does not run in:
- Safe-boot mode.
- On Windows 2000 from a remote desktop connection.
- When setup is installed by a "run as" command.
To resolve this issue
There is no workaround. These scenarios are not supported.
4. Windows Communication Foundation (WCF) Known Issues
4.1 When Using WCF Steam Types and Operations, May Get QuotaExceededException When Using Binary Encoding
When using types that derive from System.IO.Stream as input or output parameters in service operations, QuotaExceededException may be thrown if the binary encoding is being used, even though no quotas have actually been exceeded. This encoding is the default for several standard bindings, such as .NET TcpBinding.
To work around this problem, set the MaxBytesPerRead quota to the value 4200 (or some other number that is divisible by 8 but not by 16) instead of the default value of 4096. You can do this by changing the setting in your application’s configuration file. MaxBytesPerRead is contained in the ReaderQuotas subsection of the binding configuration section.
4.2 AutoComplete Transactions May Incorrectly Abort
When flowing a transaction to a WCF service, the transaction may incorrectly abort if it is committed immediately after the channel is closed. This will only affect services where TransactionAutoCompleteOnSessionClose is set to true and where the last transacted method called has TransactionAutoComplete set to false. When using System.Transactions to flow the transaction, this behavior will generate a System.Transactions.TransactionAbortedException exception.
This is a known issue that will be addressed in a future release.
To work around the issue, wait a number of seconds after closing the channel before committing the transaction.
4.3 WCF Logs Some Message Bodies Even When logEntireMessage Is Set to "False" in Configuration Files or Through WMI
By default, WCF does not log message bodies. However, in this release if logEntireMessage is set to "false" in app.config or web.config, as in the example below, or through WMI, WCF will log message bodies at the transport layer for outgoing messages.
<configuration>
<system.serviceModel>
<diagnostics>
<messageLogging logEntireMessage="false" .. />
</diagnostics>
...
</system.serviceModel>
...
</configuration>
If there is any personal information contained in the message bodies it will be visible in the log files. This is a known issue that will be addressed in a future release.
To work around this issue, edit the configuration file to remove the logEntireMessage="false” entry. Then restart the application. If logEntireMessage is not set in config, simply restart the application.
4.4 May Get a Windows Defender Warning After Installing .NET Framework 3.0 (formerly WinFX)
If your Windows Defender signatures are out of date you may receive a warning message regarding infocard.exe.
Updating your Defender signatures will resolve this issue.
4.5 Using an Untyped Message Contract with Transactional Operations Will Raise a MessageSecurityException
When calling an operation that accepts and returns parameters of type System.ServiceModel.Channels.Message while “TransactionScopeRequired = true,” an exception of type System.ServiceModel.Security.MessageSecurityException will be raised. Following this exception, the channel will be in an unusable state.
This is a known issue that will be addressed in a future release
4.6 WS-AtomicTransaction Protocol Service Startup Creates an Incorrect Application Event Log Entry
When the WS-AtomicTransaction protocol service is successfully started, an application event log entry will be created. The event description will incorrectly state that “The WS-AT protocol service was stopped.” This description can be ignored and the protocol service can be used.
This is a known issue that will be addressed in a future release.
4.7 DefaultProtectionLevels for Endpoints on the Same Contract Must Be the Same
The svcutil.exe tool reports an error when it attempts to generate multiple bindings for a single contract that:
Have different protection levels on the Typed Message parts specified at the contract levelHave different protection levels set on the bindings mapping to the above contract Currently, there is no mechanism for specifying protection levels at the binding level for individual operations or messages, so the svcutil.exe tool decorates the generated contract with those attributes. However, the current version of the svcutil.exe tool does not support multiple bindings that share the same contract but that have different protection levels set on their operations or messages. This issue will be addressed in a future release.
4.8 SOAP Faults May Not Be Reported Properly to WCF Clients When a Service Is Hosted on IIS 7
The IIS7 CustomErrors HTTP module currently prevents the transmission of SOAP faults over HTTP. This behavior interferes with WCF’s ability to properly communicate error conditions back to service consumers. Clients who encounter this error unexpectedly receive an HTML error page instead of the expected SOAP fault. In addition, the client application will raise a protocol exception.
This will be addressed in a future release.
To work around this error, add the following configuration to the application-level web.config file for any IIS7 applications hosting WCF services:
<system.webServer>
<modules>
<remove name=”CustomErrorModule” />
</modules>
</system.webServer>
4.9 WCF Ignores Reader Quotas When Using MTOM Encoding
In the current release of WCF, quotas related to reading XML (ReaderQuotas property on some standard bindings as well as on the mtomMessageEncoding binding element) are ignored when the MTOM encoding is in use. This will be addressed in a future release.
4.10 WCF May Allocate Up to MaxReceivedMessageSize Bytes per Message
In the current release, WCF may, in some circumstances, allocate up to MaxReceivedMessageSize bytes per message to buffer the message in its entirety, even if streaming is being used. This does not occur in normal streaming usage scenarios but only for some specially-constructed messages. This will be addressed in a future release.
You should not set the MaxReceivedMessageSize property to a value higher than what you are prepared to allocate per message, taking into account that multiple messages may be processed by a service simultaneously.
4.11 Windows HotFix is Required on Windows XP and Windows Server 2003 to Use WS-AtomicTransaction and COM+ Integration Functionality
The WCF WS-AtomicTransaction support and COM+ Integration functionality require a Windows hotfix (QFE) in order to work on Windows XP and Windows Server 2003. You can install the hotfix package from http://go.microsoft.com/fwlink/?linkid=46976. This supersedes the previous hotfixes required for previous releases of .NET Framework 3.0 (formerly WinFX).
4.12 WS-AtomicTransaction Configuration Utility (WsatConfig.exe) Generates Incorrect SSL Certificate Registrations
When configuring certificates for secure interoperable WS-AtomicTransaction support, the WsatConfig.exe utility incorrectly configures the SSL registration for http.sys. In this state, cross-machine WS-AtomicTransaction transactions will abort and you may observe exceptions of type TransactionManagerCommunicationException. This issue will be addressed in a future release.
To work around this issue, set the correct certificate identity using the HTTP Configuration Utility (Httpcfg.exe) with the following sequence of commands:
- Run regedit.exe and navigate to the following key:
- HKEY_LOCAL_MACHINE\Software\Microsoft\Wsat\3.0 - Note the value of the X509CertificateIdentity reg key.
- Run "HttpCfg.exe delete ssl -i 0.0.0.0:<port>" where <port> is the desired port registration to delete.
- Run "HttpCfg.exe set ssl -i 0.0.0.0:<port> -f 2 -h <hash>" where <port> is the desired port to use for WS-AtomicTransaction communication and <hash> is the value of the X.509 reg key noted above.
HttpCfg.exe is included in the “Windows XP Service Pack 2 Support Tools” pack for current Windows platforms, available on the Microsoft Download Center, and is also include in the Windows SDK for Windows Vista.
4.13 FileNotFoundException Occurs When Running ServiceModelReg.exe on Windows Vista
On Windows Vista, ServiceModelReg.exe may fail with the following message:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
This is due to an incomplete installation of the Windows Activation Service (WAS). Ensure that all components of WAS are installed prior to running ServiceModelReg.exe. To do so, complete the following steps:
- Open the "Turn Windows Features On or Off" dialog by clicking Start -> Control Panel -> Programs and clicking the "Turn Windows Features On or Off link."
- In the tree view, select the "Windows Activation Service" checkbox.
- Expand the "Windows Activation Service" checkbox and ensure the following sub-components are also selected:
- .NET Environment
- Configuration APIs
- Process Model - Click "OK" and wait for the components to finish installing.
- Re-run ServiceModelReg.exe to register the WCF activation components with WAS.
These steps will install the minimal set of components required to support WCF service activation over non-HTTP protocols.
5. Windows Workflow Foundation Known Issues
5.1 Cannot publish activity libraries as Web services
You cannot publish an activity library project as a Web service, even though the context menu item is enabled. You can only publish workflows as web services.
5.2 Web hosting on Windows Vista requires update to web.config
A workflow cannot be published as a Web service on Windows Vista without modification. The web.config file must be modified to look like the following:
<system.webServer>
<modules>
<add name="WorkflowHost" type="System.Workflow.Runtime.Hosting.WorkflowWebHostingModule, System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="runtimeVersionv2.0" />
</modules> <directoryBrowse enabled="true" />
</system.webServer>
5.3 Using the same GUID with CreateWorkflow will return the same workflow instance
All WorkflowInstance objects that were created with the same GUID used in the CreateWorkflow method will reference the same underlying object.
5.5 Rules will be associated with a different class if your workflow class is the second class in the code file
If you have a namespace with multiple classes and your workflow class is the second class listed, then during compilation, rules will be associated with the first class in your namespace. To avoid this problem, make sure the workflow class is the first class in your namespace.
5.6 ArgumentException is thrown by ManualWorkflowSchedulerService when interacting with DelayActivity and SqlWorkflowPersistenceService
ManualWorkflowSchedulerService throws an ArgumentException when a new DelayActivity activity executes if SqlWorkflowPersistenceService loaded a workflow with the SqlPersistenceWorkflowInstanceDescription.NextTimerExpiration property set.