Update 4.0.2 for Microsoft .NET Framework 4 is now available. This update contains some new features that are based on specific requests from some top customer and on some important .NET Framework scenarios. This update also contains some important software updates for ClickOnce and for .NET Framework 4-based Windows Presentation Foundation (WPF) applications.
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 update:
Update 4.0.1 for Microsoft .NET Framework 4 - Runtime Update
Therefore, this update is a cumulative update. Any application built for the .NET Framework 4.01 can run on a computer that has the .NET Framework 4 and the Update 4.0.2 runtime installed. We recommend that applications built for the Microsoft .NET Framework 4.0.1 be upgraded to the Update 4.0.2 runtime. However, this upgrade is optional.
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.
In SQL Server code named "Denali," AlwaysOn is introduced as a High Availability topology. With this topology, secondary nodes can be accessed by read workloads. To do this, secondary nodes must only accept read-only connections. This operation requires a special intent lock to be passed together with a connection. To meet this requirement, and also to keep the connectivity information decoupled from the application, SqlClient includes the following new connection string keywords:
ApplicationIntent This keyword is passed as a connection string parameter. When this keyword is used, applications can directly connect to a read-only secondary server, or can be automatically redirected to secondary servers in an availability group.
MultiSubnetFailover This keyword supports fast failover connectivity for geographically-distributed topologies.
For more information about AlwaysOn, visit the following Microsoft website:
SQL Server Express Local Database Runtime support in SqlClient
SQL Server Express LocalDB is a new installation and execution mode of SQL Server Express that runs as a stand-alone executable and that requires a minimum amount of effort for installation. When developers connect to database files directly, a transparent SQL Server Express infrastructure runs in the background. For current SQL Server technology, LocalDB offers a Run As Normal User (RANU) user instance in a smaller package.
SqlClient adds support for SQL Server Express LocalDB connectivity that can be used by a developer.
For more information about SQL Server Express LocalDB, visit the following Microsoft website:
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To install this update, you must have the following software installed:
Windows Installer 3.1 or a later version of Windows Installer.
To obtain the latest version of Windows Installer, visit the following Microsoft website:
You have to restart the computer after you install this update if the files that are being updated are locked or are being used when you install this update.
Known issues with this update
Consider the following scenario:
You create an ASP.NET Framework application in Microsoft Visual Studio 2010 Service Pack 1 (SP1) that targets the .NET Framework 4.0.2.
You deploy the application on a server. The server has the .NET Framework 4 and this update installed.
You try to access the application from a client computer.
In this scenario, you receive the following error message:
: An error occurred during the processing of a configuration file that is required to service this request. Please review the specific error details here and change your configuration file appropriately.
Parser Error Message
: The 'targetFramework' attribute in the <compilation> element of the Web.config file is used only to target version 4.0 and later of the .NET Framework (for example, '<compilation targetFramework="4.0">'). The 'targetFramework' attribute currently references a version that is later than the installed version of the .NET Framework. Specify a valid target version of the .NET Framework, or install the required version of the .NET Framework.
Line 2: <configuration>
Line 3: <system.web>
Line 4: <compilation debug="false" targetFramework=".NETFramework, version=v4.0.2" />
Line 5: </system.web>
Line 6: </configuration>
This issue occurs because the ASP.NET code cannot correctly parse the target framework version that is specified in the Web.config file.
To resolve this issue, install update 2468871.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Microsoft .NET Framework 4 Platform Update 1 - Runtime Update
The global version of this update uses a Microsoft Windows Installer package to install the update. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.