Article ID: 945826 - View products that this article applies to.
This article lists information about problems that are fixed in the Microsoft .NET Framework 3.0 Service Pack 1.
The .NET Framework 3.0 Service Pack 1 fixes the problems that are described in the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/932471/ )FIX: Error message when you try to open or to create a protected XPS document by using the XPS viewer that is included with the .NET Framework 3.0: "Cannot open this document because your permissions have expired"
(http://support.microsoft.com/kb/932816/ )FIX: You experience various problems in Windows Workflow Foundation
(http://support.microsoft.com/kb/935314/ )FIX: You may experience issues with Windows Communication Foundation peer channel connections
(http://support.microsoft.com/kb/935315/ )The COM+ application cannot start when you use the COM+ Service Model Configuration tool to expose the COM+ components in the COM+ application
(http://support.microsoft.com/kb/935434/ )FIX: Error message in FIPS-compliant systems when you use Windows Communication Foundation to serialize generic types: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"
(http://support.microsoft.com/kb/936123/ )FIX: Error message when you open a workflow by using the workflow designer in Visual Studio 2005: "Error loading workflow"
(http://support.microsoft.com/kb/936512/ )FIX: A memory leak occurs when you send many messages by using the NetMsmq transport in the .NET Framework 3.0
(http://support.microsoft.com/kb/938758/ )FIX: The Unload method may stop responding (hang) in a Windows Workflow Foundation project
(http://support.microsoft.com/kb/942520/ )FIX: You may experience slow performance when you run a Windows Communication Foundation application
For an overview of the .NET Framework, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/zw4w595w(VS.71).aspxTo download the Microsoft .NET Framework 3.5, visit the following Microsoft Web site: