Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. An update is available for the .NET Framework 3.5 on Windows 8 and Windows Server 2012: June 2013

An update is available for the .NET Framework 3.5 on Windows 8 and Windows Server 2012: June 2013

View products that this article applies to.

Introduction

An update for the Microsoft .NET Framework 3.5 is available. For more information about the issues that this update resolves, see the "Issues that this update resolves" section.

↑ Back to the top

More Information

How to obtain this update

Microsoft Download Center

The following file is available for download from the Microsoft Download Center:

Download Download the 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.

Restart requirement

You have to restart the computer after you apply this update if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this update.

Command-line switches for this update

For more information about the various command-line switches that are supported by this update, visit the following MSDN website:
Command-Line options

Update replacement information

This update does not replace any previously released update.

How to uninstall this update

To remove this update, use the Programs and Features item in Control Panel.
File information
The global 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.

GDR service branch

For all supported x86-based versions of Windows Server 2012, Windows 8
File nameFile versionFile sizeDateTime
system.web.extensions.dll3.5.30729.64031,282,04819-Apr-201322:05
system.web.extensions.dll3.5.30729.64031,282,04819-Apr-201322:05
For all supported x64-based versions of Windows Server 2012, Windows 8
File nameFile versionFile sizeDateTime
system.web.extensions.dll3.5.30729.64031,282,04819-Apr-201322:05
system.web.extensions.dll3.5.30729.64031,282,04819-Apr-201322:05
system.web.extensions.dll3.5.30729.64031,282,04819-Apr-201322:05

LDR service branch

For all supported x86-based versions of Windows Server 2012, Windows 8
File nameFile versionFile sizeDateTime
system.web.extensions.dll3.5.30729.70431,282,04819-Apr-201322:06
system.web.extensions.dll3.5.30729.70431,282,04819-Apr-201322:06
For all supported x64-based versions of Windows Server 2012, Windows 8
File nameFile versionFile sizeDateTime
system.web.extensions.dll3.5.30729.70431,282,04819-Apr-201322:06
system.web.extensions.dll3.5.30729.70431,282,04819-Apr-201322:06
system.web.extensions.dll3.5.30729.70431,282,04819-Apr-201322:06

↑ Back to the top

Issues that this update resolves

Issue 1

Consider the following scenario:
  • You use a browser which can’t be recognized by ASP.NET, such as Amazon Kindle Fire 2 or Internet Explorer 11, to access an ASP.NET-based webpage.
  • You trigger a postback event on that webpage.
In this scenario, the postback operation fails, and you receive the following error message:
"Script Error encountered", "'__doPostBack' is undefined"

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Issue 2

Consider the following scenario:
  • An ASP.NET website renders different content based on the user browser.
  • A user uses Internet Explorer 11 to visit this ASP.NET website.
In this scenario, ASP.NET cannot recognize Internet Explorer 11 and will not render the content correctly. After the user applies this hotfix, Internet Explorer 11 can be recognized as InternetExplorer by ASP.NET.

Issue 3

Consider the following scenario:
  • An ASP.NET page contains an update panel, and inside it there is an ImageButton. If user clicks ImageButton, it will trigger a partial postback event and the server side click event.
  • A user uses Internet Explorer 10 or a later version to access this ASP.NET page, and then clicks the Imagebutton.
In this scenario, the partial postback fails, and the server side click event is not fired.

Issue 4

Consider the following scenario:
  • There is an ASP.NET page that contains a menu control.
  • A user uses Internet Explorer 11 to access that page, and presses Tab to switch the focus between the menu control and other controls.
In this scenario, the user will receive the following JavaScript error message:
Error: SCRIPT5007: Unable to get value of the property 'toLowerCase': object is null or undefined
Note 1 There is a configuration switch to be used to revert back to the old behavior: 
<appSettings>
<add key="aspnet:UseLegacyBrowserCaps" value="true" />
</appSettings>

↑ Back to the top

Keywords: kbsurveynew, kbexpertiseadvanced, kbfix, atdownload, kb

↑ Back to the top

Article Info
Article ID : 2836947
Revision : 1
Created on : 1/7/2017
Published on : 1/28/2014
Exists online : False
Views : 210