This is Update 4.0.3 for Microsoft .NET Framework 4 containing a set of new features addressing top customer feature requests and important .NET Framework scenarios.
Update 4.0.3 for Microsoft .NET Framework 4 is now available. This update includes a set of new features and fixes some bugs, based on top customer requests and the .NET Framework scenarios.
This update release updates only the runtime files for the Microsoft .NET Framework 4. For more information about the details of this update, see the "More Information" section.
- This update contains all the runtime changes from the following updates:
- We do not support any application that this update was used to build on any prerelease version of the .NET Framework 4, such as a Beta. Additionally, we recommend that any such application be upgraded to at least the Microsoft .NET Framework 4 RTM.
Feature 1: SustainedLowLatency added to GCLatencyMode
Some applications perform time-sensitive operations throughout the day, during which interruptions from long full blocking garbage collection could be disruptive. For example, applications that need quick response times because of financial market data changes during trading hours. If an application has a large managed heap in this environment, it could become unresponsive for long periods of time if full blocking garbage collection occurs.
Feature 2: Support running Workflows in partial trustWorkflows that use Windows Workflow Foundation 4 (WF4) can run only in fully trusted application domains. This update enables WF to run in partially trusted environments. The scope of the change is enabling the core workflow runtime (execution model, activity and data model, tracking, and serialization) to run in partial trust. To enable this change, some WF assemblies are made conditional AllowPartiallyTrustedCallersAttribute (APTCA).
Feature 3: Enable WF messaging activities across multiple hostsWF4 messaging activities (Send, Receive, ReceiveReply, SendReply, and so on) use WCF to send and receive messages. This update introduces a new WF extension that is used by these activities to send or receive messages (or both). The extension has to be provided by the host. If the extension is not present, the WF4 behavior and execution is preserved (no changes to current code path). If the extension is present, the activities call the methods in the extension.
Feature 4: XLinq and DataAnnotations added to .NET Framework 4 Portable Class LibrariesSupport for System.Xml.Linq.dll and System.ComponentModel.DataAnnotations.dll has been added to the Portable Class Library project when targeting .NET Framework 4.0.3. For more information about how to install Portable Class Library support, visit the Portable Class Library article on MSDN.
Feature 5: Support for Correlated Connection ID in SqlClientIn Microsoft SQL Server 2012, capability to correlate a connection ID between the client and the server is added. With this update SqlClient will send the connection ID information so that it can be logged on the server side. Additionally, the following capabilities are added to SqlClient to provide ways to retrieve the connection ID on the client side if it is available:
Issues that this update resolves
Issue 1: Cannot set the WWW-Authenticate HTTP Response header in self-hosted WCF service scenarios
If you have a self-hosted WCF service, you could not send a www-Authenticate HTTP header in the response message. This is required for many custom authentication scenarios, such as enabling OAuth. This limitation was removed.
Issue 2: Self-hosted BasicHttp service that uses https enabled fails in partial trust
Issue 3: WCF: Identical binding extension elements in machine.config and app.config throws an exception
With this update, we have made the System.Deployment platform check more flexible for ClickOnce applications.
This package contains updated design-time files for Visual Studio 2010 SP1 corresponding to Update 4.0.3 for Microsoft .NET Framework 4. For further details about the contents of Update 4.0.3 for Microsoft .NET Framework 4 – Design-time Update please refer to the Knowledge Base Article KB2600214.
This design time package installs the following individual packages:
- Update 4.0.3 for Microsoft .NET Framework 4 – Runtime Update (KB2600211)
- Multi-Targeting Pack for the Microsoft .NET Framework 4.0.3 (KB2600213)
- Visual Studio 2010 SP1 Update for enabling workflow state machine designer (KB2495593)
This update adds support for designing and developing applications for the Update 4.0.3 for Microsoft .NET Framework 4 by using Microsoft Visual Studio 2010 SP1 or later. The MT Pack adds new reference assemblies, IntelliSense files, and other supporting files. For further details about the contents of this Targeting Pack refer to the Knowledge Base Article KB2600213.
Update 4.0.3 for the Microsoft .NET Framework 4 is now available for download. This is the third platform update that offers new features on top of the initial release for the .NET Framework 4. You can learn about earlier platform updates via the following links: Update 4.0.2 and Update 4.0.1.
Update 4.0.3 introduces five new features spanning the common language runtime, Windows Workflow Foundation (WF), and SqlClient. In addition, Update 4.0.3 includes all the features released in Update 4.0.1 and 4.0.2.
That says about it all... When/If I find any more information or details I'll update this post.
Update 3/5/2012 6:41PM PST:
Added the Update 4.0.3 for the Microsoft .NET Framework 4 post
Update 3/6/2012 6:19AM PST:
Fixed link to the Portable Class Library article (BTW, the link in the actual KB is busted as of the writing of this, but if you look at the busted URL you can tell the intended link, which is what I did...)