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. Hotfix rollup 3099848 for the .NET Framework 4.6 in Windows Server 2012, Windows 8, and Windows RT

Hotfix rollup 3099848 for the .NET Framework 4.6 in Windows Server 2012, Windows 8, and Windows RT

View products that this article applies to.

This article describes hotfix rollup 3099848, which is available for the Microsoft .NET Framework 4.6. For more information about the issues that this hotfix rollup fixes, see the "Issues that this hotfix rollup fixes" section.

↑ Back to the top

Resolution

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, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note 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.

↑ Back to the top

More Information

Prerequisites

To apply this hotfix, you must have the .NET Framework 4.6 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

Issue 1

The System.Windows.Markup.XamlWriter.Save method can’t turn off indentation for an element that has the xml:space="preserve" setting. This results in additional spaces being added to the element. For example, a paragraph represented by the following XAML will be transformed into incorrect XAML by XamlWriter.Save method:

<Paragraph>
<Span>
<Run Text="Test"/>
</Span>
<Run Text=" "/>
</Paragraph>
Incorrect XAML 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 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.

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.

↑ Back to the top

Keywords: kbfix, kbqfe, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 3099848
Revision : 1
Created on : 1/7/2017
Published on : 11/18/2015
Exists online : False
Views : 482