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.

Hotfix rollup 3146710 for the .NET Framework 4.5.2, 4.5.1, and 4.5 on Windows


View products that this article applies to.

This article describes hotfix rollup 3146710 that's available for the Microsoft .NET Framework 4.5.2, 4.5.1, and 4.5. For more information about the issues that the hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.

↑ Back to the top


Resolution

The following files are available for download from the Microsoft Download Center:

Download Download the x86 package now.

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


Note To verify the hotfix update version, check the value of the Release keyword to determine the installed version. To be forward-compatible, you can check for a value that's greater than or equal to the value that's listed in the following table.

Hotfix rollup version Value of the Release DWORD 
Hotfix rollup 3146710 for the .NET Framework 4.5 and later versions 380035
For more information about how to determine the .NET Framework versions, see How to: Determine Which .NET Framework Versions Are Installed

↑ Back to the top


More Information

Prerequisites

To apply this hotfix, you must have the .NET Framework 4.5.2, 4.5.1, or 4.5 installed.

Restart requirement

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

Hotfix replacement information

This hotfix package doesn't replace a previously released hotfix package.

↑ Back to the top


Issues that this hotfix rollup fixes

ASP.NET

Contention and bad performance on System.Web.BufferAllocator when you run a web application on computers that have more than 32 cores.

Fix: The contention has been eliminated by removing the global lock in System.Web.BufferAllocator.​

Windows Forms

Windows Forms PrintPreviewDialog UI is initialized very slowly when the following conditions are true:

  • A network printer is used.
  • Users preference for this printer, such as duplex settings, are changed.
We have added a performance optimization to this scenario. If page settings were not changed for a specific page, we are not re-applying (by accessing the printer spooler) printer settings for this page. If the application is changing printer settings by using the QueryPageSettings event handler, print preview generation performance for the affected pages is not improve even if the opt-in flag is set.

In order to opt in to this optimization, the following key should be added to the App.config file:

On the .NET Framework 4.5.2:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
< appSettings >
< add key="OptimizePrintPreview" value="true" />
< /appSettings >
</configuration>
On the .NET Framework 4.6 or a later version:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
< runtime>
< AppContextSwitchOverrides value = "Switch.System.Drawing.Printing.OptimizePrintPreview=true" />
< /runtime>
</configuration>
If an application can run on either version of the .NET Framework, use both switches in the same file.

To opt out, change the switched or set values to false. ​

ClickOnce

ClickOnce has been updated to support TLS 1.1 and 1.2. ClickOnce automatically detects which TLS protocol is required at runtime. No additional steps are required within the ClickOnce application to enable this feature.

Note ClickOnce continues to support TLS 1.0 for the foreseeable future, even though it is no longer considered acceptable for PCI Compliance.​

↑ Back to the top


Keywords: kbfix, kbsurveynew, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3146710
Revision : 1
Created on : 1/7/2017
Published on : 4/13/2016
Exists online : False
Views : 203