Article ID: 2162169 - View products that this article applies to.
Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.
Expand all | Collapse all

On This Page

Introduction

A beta version of an update rollup is available for the .NET Framework 4. This update rollup includes all the previous update packages that are described in the following Microsoft Knowledge Base (KB) articles:
2183292 FIX: "Failure sending mail" error message when you send an email message by using a .NET Framework 4.0-based application that uses the "System.Net.Mail.SmtpClient" class if the email attachment is larger than 3 MB
2413613 A shortcut menu may appear far away from the mouse pointer when you run a Windows Presentation Foundation application that is based on the .NET Framework 4
2298853 FIX: Visual Studio 2010 error: "Error 1 error MSB4014: The build stopped unexpectedly because of an internal failure"
This update rollup package also resolves some issues and provides some features that were not documented in a previously released KB article. For more information about these issues and features, see the "More information" section.

Note This beta version of a .NET Framework 4 update rollup is a part of Visual Studio 2010 Service Pack 1 (SP1) Beta. For more information about Visual Studio 2010 SP1 Beta, visit the following Microsoft Download website:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=11ea69cb-cf12-4842-a3d7-b32a1e5642e2&displaylang=en

RESOLUTION

Download information


The following files are available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the beta version of the update for the .NET Framework 4 package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 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.

Prerequisites

To apply this update, you must have the .NET Framework 4 or the .NET Framework 4 Client Profile installed.
To install this update, you must have Windows Installer 3.1 or a later version installed. To obtain the latest version of Windows Installer, visit the following Microsoft website:
Download Windows Installer 4.5 Redistributable

Command-line switches for this update


For information about the various command-line switches that are supported by this update, see the Windows Installer command-line switches document.

For more information about Windows Installer, visit the Windows Installer Windows Installer Microsoft Developer Network (MSDN) website.

Restart requirement

This update does not require a system restart after you apply the update unless the files that are being updated are locked or are being used. However, this update restarts all Internet Information Services (IIS)-related services when you install this update.

Update replacement information

This update replaces the following updates:
2183292 FIX: "Failure sending mail" error message when you send an email message by using a .NET Framework 4.0-based application that uses the "System.Net.Mail.SmtpClient" class if the email attachment is larger than 3 MB
2413613 A shortcut menu may appear far away from the mouse pointer when you run a Windows Presentation Foundation application that is based on the .NET Framework 4
2298853 FIX: Visual Studio 2010 error: "Error 1 error MSB4014: The build stopped unexpectedly because of an internal failure"

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aspnet_compiler.exe4.0.30319.20830,04804-Nov-201006:54x86
Aspnet_compiler.exe4.0.30319.37230,04804-Nov-201006:54x86
Aspnet_compiler.exe4.0.30319.20829,02404-Nov-201007:06x64
Aspnet_compiler.exe4.0.30319.37229,02404-Nov-201007:07x64
Aspnet_wp.exe4.0.30319.20832,59204-Nov-201006:54x86
Aspnet_wp.exe4.0.30319.37232,59204-Nov-201006:54x86
Aspnet_wp.exe4.0.30319.20840,78404-Nov-201007:06x64
Aspnet_wp.exe4.0.30319.37240,78404-Nov-201007:07x64
Clr.dll4.0.30319.2086,732,61604-Nov-201004:59x86
Clr.dll4.0.30319.3726,732,61604-Nov-201005:01x86
Clr.dll4.0.30319.3729,798,98404-Nov-201005:37x64
Clr.dll4.0.30319.2089,798,98404-Nov-201005:38x64
Clrjit.dll4.0.30319.208385,86404-Nov-201004:59x86
Clrjit.dll4.0.30319.372385,86404-Nov-201005:01x86
Mscordacwks.dll4.0.30319.2081,141,59204-Nov-201004:59x86
Mscordacwks.dll4.0.30319.3721,141,59204-Nov-201005:01x86
Mscordacwks.dll4.0.30319.3721,513,30404-Nov-201005:37x64
Mscordacwks.dll4.0.30319.2081,513,30404-Nov-201005:38x64
Microsoft.build.tasks.v4.0.dll4.0.30319.2081,065,32804-Nov-201006:54x86
Microsoft.build.tasks.v4.0.dll4.0.30319.3721,065,84004-Nov-201006:54x86
Microsoft.build.tasks.v4.0.dll4.0.30319.2081,065,32804-Nov-201006:54x86
Microsoft.build.tasks.v4.0.dll4.0.30319.3721,065,84004-Nov-201006:54x86
Microsoft.csharp.targetsNot applicable13,03101-Nov-201011:54x86
Microsoft.csharp.targetsNot applicable13,03128-Oct-201020:43x86
Microsoft.data.entity.build.tasks.dll4.0.30319.20839,29604-Nov-201006:54x86
Microsoft.data.entity.build.tasks.dll4.0.30319.37239,29604-Nov-201006:54x86
Microsoft.data.entity.build.tasks.dll4.0.30319.20839,29604-Nov-201006:54x64
Microsoft.data.entity.build.tasks.dll4.0.30319.37239,29604-Nov-201006:54x64
Microsoft.visualbasic.targetsNot applicable13,63001-Nov-201011:54x86
Microsoft.visualbasic.targetsNot applicable13,63028-Oct-201020:43x86
Microsoft.build.commontypes.xsdNot applicable195,80422-Oct- 201002:02x86
Microsoft.build.commontypes.xsdNot applicable195,80428-Oct- 201020:40x86
Microsoft.build.commontypes.xsdNot applicable195,80422-Oct- 201002:02x64
Microsoft.build.commontypes.xsdNot applicable195,80428-Oct- 201020:40x64
Mscordbi.dll4.0.30319.208955,72804-Nov-201004:59x86
Mscordbi.dll4.0.30319.372955,21604-Nov-201005:01x86
Mscordbi.dll4.0.30319.3721,453,39204-Nov-201005:37x64
Mscordbi.dll4.0.30319.2081,453,39204-Nov-201005:38x64
Mscorlib.dll4.0.30319.2085,196,11204-Nov-201004:59x86
Mscorlib.dll4.0.30319.3725,196,11204-Nov-201005:01x86
Mscorlib.dll4.0.30319.3724,960,08004-Nov-201005:37x64
Mscorlib.dll4.0.30319.2084,960,08004-Nov-201005:38x64
Presentationcore.dll4.0.30319.2083,546,46404-Nov-201004:59x86
Presentationcore.dll4.0.30319.3723,546,46404-Nov-201005:01x86
Presentationcore.dll4.0.30319.3723,454,30404-Nov-201005:37x64
Presentationcore.dll4.0.30319.2083,454,30404-Nov-201005:38x64
Presentationframework.dll4.0.30319.2086,346,60004-Nov-201004:59x86
Presentationframework.dll4.0.30319.3726,347,11204-Nov-201005:01x86
Presentationframework.dll4.0.30319.2086,346,60004-Nov-201004:59x64
Presentationframework.dll4.0.30319.3726,347,11204-Nov-201005:01x64
Servicemodelreg.exe4.0.30319.208191,84004-Nov-201004:59x86
Servicemodelreg.exe4.0.30319.372191,84004-Nov-201005:01x86
Servicemodelreg.exe4.0.30319.372260,44804-Nov-201005:37x64
Servicemodelreg.exe4.0.30319.208260,44804-Nov-201005:38x64
Setup.dll10.0.30319.372295,24804-Nov-201005:01x86
Setupengine.dll10.0.30319.372809,30404-Nov-201005:01x86
Setupui.exe10.0.30319.37278,15204-Nov-201005:01x86
Sos.dll4.0.30319.208517,44804-Nov-201004:59x86
Sos.dll4.0.30319.372516,93604-Nov-201005:01x86
Sos.dll4.0.30319.372597,83204-Nov-201005:37x64
Sos.dll4.0.30319.208597,83204-Nov-201005:38x64
System.core.dll4.0.30319.2081,339,73604-Nov-201004:59x86
System.core.dll4.0.30319.3721,339,73604-Nov-201005:01x64
System.core.dll4.0.30319.2081,339,73604-Nov-201004:59x64
System.core.dll4.0.30319.3721,339,73604-Nov-201005:01x86
System.data.entity.design.dll4.0.30319.208805,23204-Nov-201006:54x86
System.data.entity.design.dll4.0.30319.372805,23204-Nov-201006:54x64
System.data.entity.design.dll4.0.30319.208805,23204-Nov-201006:54x64
System.data.entity.design.dll4.0.30319.372805,23204-Nov-201006:54x86
System.design.dll4.0.30319.2085,078,87204-Nov-201006:54x86
System.design.dll4.0.30319.3725,078,87204-Nov-201006:54x86
System.design.dll4.0.30319.2085,078,87204-Nov-201006:54x64
System.design.dll4.0.30319.3725,078,87204-Nov-201006:54x64
System.dll4.0.30319.2083,482,95204-Nov-201004:59x86
System.dll4.0.30319.3723,482,95204-Nov-201005:01x86
System.dll4.0.30319.2083,482,95204-Nov-201004:59x64
System.dll4.0.30319.3723,482,95204-Nov-201005:01x64
System.net.dll4.0.30319.208232,78404-Nov-201004:59x86
System.net.dll4.0.30319.372232,78404-Nov-201005:01x86
System.net.dll4.0.30319.208232,78404-Nov-201004:59x64
System.net.dll4.0.30319.372232,78404-Nov-201005:01x64
System.servicemodel.dll4.0.30319.2086,071,65604-Nov-201004:59x86
System.servicemodel.dll4.0.30319.3726,073,70404-Nov-201005:01x86
System.servicemodel.web.dll4.0.30319.208316,27204-Nov-201006:54x86
System.servicemodel.web.dll4.0.30319.372316,27204-Nov-201006:54x86
System.web.dll4.0.30319.2085,183,82404-Nov-201006:54x86
System.web.dll4.0.30319.3725,183,82404-Nov-201006:54x86
System.web.dll4.0.30319.2085,153,61604-Nov-201007:06x64
System.web.dll4.0.30319.3725,153,61604-Nov-201007:07x64
System.web.extensions.dll4.0.30319.2081,836,90404-Nov-201006:54x86
System.web.extensions.dll4.0.30319.3721,836,90404-Nov-201006:54x86
System.web.extensions.dll4.0.30319.2081,836,90404-Nov-201006:54x64
System.web.extensions.dll4.0.30319.3721,836,90404-Nov-201006:54x64
System.xml.dll4.0.30319.2082,207,56804-Nov-201004:59x86
System.xml.dll4.0.30319.3722,207,56804-Nov-201005:01x86
System.xml.dll4.0.30319.2082,207,56804-Nov-201004:59x64
System.xml.dll4.0.30319.3722,207,56804-Nov-201005:01x64
System.xml.serialization.dll4.0.30319.20811,63204-Nov-201004:59x86
System.xml.serialization.dll4.0.30319.37211,63204-Nov-201005:01x86
System.xml.serialization.dll4.0.30319.20811,63204-Nov-201004:59x64
System.xml.serialization.dll4.0.30319.37211,63204-Nov-201005:01x64
Vbc.exe10.0.30319.2082,262,34404-Nov-201004:59x86
Vbc.exe10.0.30319.3722,262,34404-Nov-201005:01x86
Vbc.exe10.0.30319.3723,236,16804-Nov-201005:37x64
Vbc.exe10.0.30319.2083,235,65604-Nov-201005:38x64
Webengine.dll4.0.30319.20814,16004-Nov-201006:54x86
Webengine.dll4.0.30319.37214,16004-Nov-201006:54x86
Webengine.dll4.0.30319.20815,69604-Nov-201007:06x64
Webengine.dll4.0.30319.37215,69604-Nov-201007:07x64
Webengine4.dll4.0.30319.208495,44004-Nov-201006:54x86
Webengine4.dll4.0.30319.372495,44004-Nov-201006:54x86
Webengine4.dll4.0.30319.208720,20804-Nov-201007:06x64
Webengine4.dll4.0.30319.372720,20804-Nov-201007:07x64
Windowsbase.dll4.0.30319.2081,303,89604-Nov-201004:59x86
Windowsbase.dll4.0.30319.3721,304,92004-Nov-201005:01x86
Windowsbase.dll4.0.30319.2081,303,89604-Nov-201004:59x64
Windowsbase.dll4.0.30319.3721,304,92004-Nov-201005:01x64
Wpfgfx_v0400.dll4.0.30319.2081,663,32004-Nov-201004:59x86
Wpfgfx_v0400.dll4.0.30319.3721,663,32004-Nov-201005:01x86
Wpfgfx_v0400.dll4.0.30319.3722,153,81604-Nov-201005:37x64
Wpfgfx_v0400.dll4.0.30319.2082,153,81604-Nov-201005:38x64
Wpftxt_v0400.dll4.0.30319.208916,31204-Nov-201004:59x86
Wpftxt_v0400.dll4.0.30319.372916,31204-Nov-201005:01x86
Wpftxt_v0400.dll4.0.30319.3721,221,46404-Nov-201005:37x64
Wpftxt_v0400.dll4.0.30319.2081,221,46404-Nov-201005:38x64
Note The version number 4.0.30319.208 is built by the .NET Framework GDR; the version number 4.0.30319.372 is built by the .NET Framework LDR.

MORE INFORMATION

Issues that this update rollup package resolves

This update rollup package resolves the following issues that are related to the .NET Framework 4.

Issue 1

Consider the following scenario:
  • You create a Visual Studio 2010-based Add-in application. The Add-in application enumerates several projects by using a background thread.
  • You run an instance of Visual Studio 2010 and the Add-in application.
  • Garbage collection runs.
In this scenario, the instance of Visual Studio 2010 may stop responding.

Issue 2


Consider the following scenario:
  • You develop a .Net Framework 4-based Add-in application for Excel.
  • You run the Add-in application, and then the Application.WorkbookBeforeSave event occurs.
In this scenario, the SaveAsUI parameter in this event is always set to the TRUE value.

Issue 3

If the focus is set to a window of a Visual Studio 2010-based application when the computer enters sleep mode, a memory leak occurs when the computer resumes from sleep mode.

Issue 4

When a .NET Framework 4-based Windows Presentation Foundation (WPF) application tries to load some text from a .ttf file, the text is displayed incorrectly. Additionally, an access violation occurs, and then the application crashes.

Note The stack trace resembles the following:
06bdeafc 71086dd5 dwrite!TrueTypeRasterizer::Implementation::ReleaseSfntFragment()+0x1f
06bdeb5c 7108d327 dwrite!sfac_GetSbitBitmap()+0x428
06bdec10 7108d4d8 dwrite!GetSbitComponent()+0xb5

Issue 5

When you perform a touch manipulation in a .NET Framework 4-based WPF application on a multi-touch screen, the application crashes, or the *.vshost.exe process crashes. For example, the application crashes when you try to scroll up or scroll down.

Issue 6

When you try to select multiple items on the Pending Changes window in Visual Studio 2010, the Visual Studio IDE disappears, and a Dr. Watson error is incorrectly not generated.

Issue 7

Consider the following scenario:
  • You run a Visual Studio 2010 on a 64-bit version operating system.
  • You debug an application.
  • You enable the managed debugging assistants (MDA).
  • You try to close the application in the IDE.
In this scenario, the raceOnRCWCleanup MDA incorrectly runs.

Issue 8

When you scroll in a .NET Framework 4-based WPF application while the text in a tab control is being formatted, the application runs slowly.

Issue 9

When you try to host a webpage that has the targetFramework property set as the .NET Framework on a Server Core, you receive the following error message:
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify 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.

Source Error:
Line 2: <configuration>
Line 3: <system.web>
Line 4: <compilation debug="false" targetFramework=".NETFramework, version=v4.0" />
Line 5: </system.web>Line 6: </configuration>

Issue 10

Symptom

Consider the following scenario:
  • You create a Visual Studio 2010 application that contains a Dataset database.
  • You drop some tables from Dataset Designer.
  • You check the order of the tables in Dataset Designer.
In this scenario, the tables are sorted incorrectly.

Cause

This issue occurs because of an error in the TableAdapterManager class in Visual Studio 2010.

Issue 11

When a client requests the RESTful web service in a .asmx or a .svc file by using the ASP.NET pipeline and by using the extension-less URL handling, the state of the request might incorrectly change.

Issue 12

In the .NET Framework 4.0, the Application_Start and PreAppStart methods do not have access to the HttpUtility.HtmlEncode method and to the related APIs.

Issue 13

When you try to run a C# or Visual Basic application, the application does not run if an Entity Data Model (EDM) references a database project. Additionally, the debugging features of the application do not work.

Issue 14

When you use SQL providers, the following issues occur:
  • An exception is thrown on the garbage collection thread.
  • A Dr. Watson error occurs, and you receive an error message that resembles the following:
    Application: webdev.webserver20.exe
    Blamed Symbol:
    SYSTEM.DATA.NI.DLL!System.Data.ProviderBase.DbConnectionInternal.PrePush
    Exception code: system.invalidoperationexception
    Event Sub type: Clr20r3
  • The w3wp.exe process crashes.

    Note The w3wp.exe process is a web hosting process.

Issue 15

Symptom

The SqlDataSource class does not support a parameter that is used to access data in a Microsoft SQL Server Compact Edition database.

Cause

This issue occurs because Microsoft SQL Server Compact cannot support a parameter in the SqlDataSource class.

Issue 16

Symptom

When you try to run an ASP.NET webpage, you receive the following error message:
HttpContext.User is supposed to be a MyWindowsPrincipal.

Cause

The issue occurs because the Extensionless URL handler passes the parent IHttpUser interface to the child requests. Therefore, the child requests skip the authentication process.

Issue 17

Consider the following scenario:
  • You have a Visual Studio 2010-based project that has an Entity Data Model (EDM). The EDM references a database that is medium or large in size. For example, the database contains 500 tables.
  • You try to reverse engineer the tables.
In this scenario, reverse engineering the tables requires a long time. For example, reverse engineering 500 tables requires 14 minutes.

Issue 18

Consider the following scenario:
  • You install Visual Studio 2010 Service Pack 1 (SP1) Beta on a computer that is running Internet Information Services (IIS) 6.0.
  • You set the isolation mode to IIS 5.0.
  • You host a webpage in IIS 6.0.
In this scenario, you receive the following error message when you try to access the webpage:
503 - Service unavailable.

Issue 19

After you install a hotfix package that applies the .NET Framework 4.0, all services that are hosted on Windows Process Activation Services (also known as WAS) may be turned off. Additionally, the services cannot be restarted until you restart the computer. An example of a service is a WAS-hosted Windows Communication Foundation (WCF) service.

The following are the affected activation services:
    Non-HTTP Activation
    • MSMQ Activation
    • Named Pipes Activation
    • TCP Activation

  • TCP Port Sharing

Issue 20

Consider the following scenario:
  • You have an ASP.NET website that contains a WCF service. The website targets to an earlier version of the .NET Framework 4.0.
  • You do not click to select the Allow this precompiled site to be updatable check box in the Publish Web Site wizard in Visual Studio 2010.
  • You publish the website.
  • A client tries to access the WCF service.
In this scenario, the WCF service does not respond to the client request. Additionally, the .svc.compile file incorrectly references the .NET Framework 4.0.

Note The .svc.compile file is generated by the publishing process.

Features that this update rollup package introduces

This update rollup package introduces the following features that are related to the .NET Framework 4.

Feature 1


This update rollup enables ASP.NET to support multiple IIS configuration systems in a design mode. Therefore, Visual Studio Web Designer supports IIS Express. Additionally, Visual Studio Web Designer lets different projects of Visual Studio Solution to target different versions of IIS.

Feature 2

When a shadow cache assembly that is turned into a symbolic link to the same file is validated, the size of the assembly is not checked. Therefore, ASP.NET uses the Optimization for Shared Web Hosting.

Feature 3

New syntax lets you define a TextBox control that is HTML5 compatible. For example, the following code defines a TextBox control that is HTML5 compatible:
<asp:TextBox runat="server" type="some-HTML5-type" />

Properties

Article ID: 2162169 - Last Review: June 25, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft .NET Framework 4
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced atdownload KB2162169

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com