This article describes hotfix rollup 3099856. This hotfix rollup is 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.
The offline package can be used in situations in which the web installer can't be used because of a lack of Internet connectivity. We recommend that you use the web installer instead of the offline package whenever it's possible for optimal efficiency and bandwidth requirements.
A supported hotfix is now available from Microsoft. However, it's intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To fix this problem, contact Microsoft Customer Support Services to get the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will fix your problem. The usual support costs will apply to additional support questions and issues that don't qualify for the specific update in question.
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 "Release" DWORD
Hotfix rollup 3099856 for the .NET Framework 4.5 and later versions
For more information about how to determine versions of the .NET Framework, see the following Microsoft Developer Network (MSDN) article:
To apply this hotfix, you must have the .NET Framework 4.5.2, 4.5.1, or 4.5 installed.
You must 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
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 that are 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:
<Run Text=" "/>
Incorrect XAML that is created by the XamlWriter.Save method:
<?xml version="1.0" encoding="utf-16"?>
<Span>Test</Span> <Run> </Run></Paragraph>
Expected (correct) XAML:
<?xml version="1.0" encoding="utf-16"?>
<Paragraph xml:space="preserve"><Span>Test</Span> <Run> </Run></Paragraph>
Some content is missing in printouts if transparency is used in Windows 7 and earlier versions. For example, some content in a table border could be missing and result in a blank area in printouts.
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.
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.
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.
This hotfix enables Transport Layer Security (TLS) 1.1 and 1.2 for SQL Server connectivity in System.Data.dll.