Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Update to .NET Framework 4

Update to .NET Framework 4

This item in japanese

A General Distribution Release of .NET 4 was published on the 11th of June. This includes numerous fixes and features, many of which were previously published as individual hot fixes. There are also updates to the HTML 5 and portable library support. For your convenience we have sorted the fix list by technology. For the complete list, including file versions, see KB 2468871.


  • Failure Sending Emails with Attachments that are larger than 3 MB


  • WPF application crashes if the source object of a data binding in a control is an element that is defined outside the name scope of the control
  • A shortcut menu may appear far away from the mouse pointer
  • 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.
  • When you perform a touch manipulation on a multitouch screen, the application crashes, or the *.vshost.exe process crashes. For example, the application crashes when you try to scroll up or to scroll down.
  • 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.

Visual Studio

  • MSB4014: The build stopped unexpectedly because of an internal failure
  • Visual Studio 2010 may crash because an Add-in enumerated projects in the background
  • Memory leaks when resuming from sleep mode
  • When you try to select multiple items in the Pending Changes window in Visual Studio 2010, the Visual Studio IDE disappears, and a Dr. Watson error is not generated.
  • When you try to run a Microsoft Visual C# or Microsoft 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.
  • When you request an .xap file through the Cassini in Visual Studio 2010, the MIME type of the returned response is "application/octet-stream" instead of the expected "application/x-silverlight-app."
  • In the Visual Studio 2010 IDE, you attach the debugger to a sqlservr.exe process. You set a breakpoint at a managed SQL function or at a managed stored procedure. The symbol file is loaded correctly, and a solid red dot appears. However, Visual Studio does not break at the breakpoint.

Visual Basic

  • You use the My namespace in a Visual Basic project. When you add an explicit reference to the Microsoft.VisualBasic.dll component to the project, the My namespace cannot work correctly.
  • You run a Visual Basic application that contains a Visual Basic Core assembly on an operating system that does not have the Visual Basic runtime. If the application contains a SyncLock statement on a variable of type Object, you may receive an error message that resembles the following: Requested operation is not available because the runtime library function 'Microsoft.VisualBasic.CompilerServices.ObjectFlowControl.CheckForSyncLockOnValueType' is not defined.


  • When you try to host a webpage that has the targetFramework property set as the .NET Framework on a Server Core, you receive a parser error message.
  • When a client requests the RESTful web service in an .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.
  • In the .NET Framework 4, the Application_Start and PreAppStart methods do not have access to the HttpUtility.HtmlEncode method and to the related APIs.
  • An exception is thrown on the garbage collection thread when you use SQL providers.
  • When you try to run an ASP.NET webpage, you receive the following error message: HttpContext.User is supposed to be a MyWindowsPrincipal.
  • Assume that you build a web application on a computer and then publish the application on a different computer. When you use Visual Studio 2010 to attach the application, managed methods cannot be shown because of missing symbols for assemblies.
  • The simplified web application paradigm that is called Plan 9 MVC is released more frequently than ASP.NET. However, beginning with version 2, versions are not set as full trust. Therefore, many features that require full trust cannot work correctly. This update sets the versions of Plan 9 later than version 2 to fully trust.

New Features

  • ASP.NET supports multiple IIS configuration systems in a design mode and Visual Studio Web Designer lets different Visual Studio Solution projects target different versions of IIS.
  • 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 Optimization for Shared Web Hosting.
  • 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" />
  • A new switch is added for the Visual Basic compiler that allows for server control output of HTML5-friendly elements. For example: <asp:TextBox runat="server" type="some-HTML5-type" />
  • In earlier versions of the .NET Framework, all Visual Basic applications automatically had a runtime dependency added. The dependency was with the Visual Basic Runtime library file, Microsoft.VisualBasic.dll. With this update, a command-line option can be set to remove this dependency. Some functionality of the Visual Basic Runtime is embedded in the application, and other functionality is no longer available with the switch set.
  • Changes to the support portable libraries. These changes include API updates and binder modifications. This update enables the CLR to bind successfully to portable libraries so that a single DLL can run on the .NET Framework 4, on Silverlight, on Xbox, or on the Windows Phone. This update adds public Silverlight APIs to the .NET Framework 4 in the same location. The API signatures will remain consistent across the platform. All modifications are 100 percent compatible and will not break any existing code.
  • The update extends the support of the portability files to compile Silverlight 5 XAML files.

Rate this Article