This article describes hotfix rollup 3099844. This hotfix rollup is available for the Microsoft .NET Framework 4.5.2, 4.5.1, and 4.5 on Windows 8, Windows Server 2012, and Windows RT. For more information about the issues that the hotfix rollup fixes, see the "More Information" section.
Resolution
Download information
The following files are available for download from the Microsoft Download Center:Download the x86-based hotfix package now.Download the x64-based hotfix 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.
More Information
Prerequisites
To apply this hotfix, you must have the .NET Framework 4.5.2, 4.5.1, and 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.
Issues that this hotfix rollup fixes
Issue 1
The System.Windows.Markup.XamlWriter.Save method can’t turn off indentation for an element that has xml:space="preserve." This results in additional spaces being added to the element. For example, a paragraph that is represented by the following XAML will be transformed into an incorrect XAML by the XamlWriter.Save method:
XAML representation of the source paragraph:<Paragraph>
<Span> <Run Text="Test"/> </Span> <Run Text=" "/> </Paragraph>
Incorrect XAML that is created by the XamlWriter.Save method:
<?xml version="1.0" encoding="utf-16"?>
<Section xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"> <Paragraph xml:space="preserve"> <Span>Test</Span> <Run> </Run></Paragraph> </Section>
Expected (correct) XAML:
<?xml version="1.0" encoding="utf-16"?>
<Section xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"> <Paragraph xml:space="preserve"><Span>Test</Span> <Run> </Run></Paragraph> </Section>
Issue 2
Some content is missing in printouts if transparency is used on Windows 7 and earlier versions. For example, some content in a table border could be missing and result in a blank area in printouts.
Issue 3
Some content is blurry in printouts if transparency is used in Windows 7 and earlier versions. This occurs even when you set the print to photographic level quality.
This hotfix improves the output quality that is obtained by using the OutputQuality.Photographic value. Be aware that documents that have better quality require larger print spooler files and longer wait times. If these side effects aren’t desirable, you can adjust the output quality of the print to High.Issue 4
When you run a Windows Presentation Foundation (WPF) touch application under the system context in Windows 7 and Windows Vista, touch functionality is lost and a crash may occur after several minutes. This issue occurs because inking is not supported in the system context in Windows 7 and Windows Vista.
This hotfix disables touch support while under the system context. Touch-to-mouse promotion still works.Issue 5
When a WPF application uses a TreeViewItem outside the context of a TreeView, the application can encounter an InvalidCastException whose stack trace starts as follows:
System.Windows.Controls.VirtualizingStackPanel.FindScrollOffset(Visual v)
Note The exception occurs when the TreeViewItem is in a virtualized list control (for example, a ListBox, DataGrid, or ListView control) that tries to find the scroll offset of the TreeViewItem or one of its descendants. (For example, declare a TreeViewItem as the root of a DataTemplate, and the DataTemplate is used as the CellTemplate of a DataGrid column.) In this situation, this exception occurs.
Issue 6
This hotfix enables Transport Layer Security (TLS) 1.1 and 1.2 for Microsoft SQL Server connectivity in System.Data.dll.