Added the link for ZDP update for Known Issues fixed by it. (#595)

* Added the link for ZDP update for Known Issues fixed by it. * Added platform information
microsoft · Jan 9, 2018 · e883180 · e883180
1 parent bc5fd0b
commit e883180
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 3 deletions.
diff --git a/... that use .NET Standard libraries might be broken when running on .NET 4.7.1.md b/... that use .NET Standard libraries might be broken when running on .NET 4.7.1.md
@@ -56,3 +56,6 @@ There are two ways to work around this issue:
  - When running on .NET Framework 4.7.1, remove the binding redirects from the app.config file for the assemblies that are now part of the .NET Framework.
  - Re-target your application to target the .NET Framwork 4.7 or .NET Framework 4.7.1.
 
+## Resolution
+
+[09-Jan-2018] The fix for this issue is included  in the [Update for .NET Framework 4.7.1 - KB4054856](http://go.microsoft.com/fwlink/?LinkId=866028) for all platforms except Windows 10 Fall Creators Update.
diff --git a/...avy use of System.Diagnostics.StackTrace might run more slowly on .NET 4.7.1.md b/...avy use of System.Diagnostics.StackTrace might run more slowly on .NET 4.7.1.md
@@ -1,9 +1,11 @@
 # Applications making heavy use of System.Diagnostics.StackTrace or Exception.StackTrace might run more slowly on the .NET Framework 4.7.1
 
 ## Symptoms
+
 An application that had acceptable performance running on the .NET Framework 4.7 or earlier versions executes more slowly when running on the .NET Framework 4.7.1
 
 ## Cause
+
 The .NET Framework 4.7.1 added support for detecting and parsing the Portable PDB file format to show file and line number information in stack traces. As part of this change, each function in a 
 stack trace has its defining module checked to determine if that module uses the Portable PDB format. Due to some differences in the internal caching policy, the 
 runtime spends far more time searching for Portable PDBs than previous .NET Framework versions spent searching for classic Windows PDBs. This causes formatted stack traces to be
@@ -12,8 +14,11 @@ produced more slowly than before.
 The issue was originally reported here: https://github.com/Microsoft/dotnet/issues/529
 
 ## Workarounds
+
 Call the [System.Diagnostics.StackTrace.#ctor(Boolean)](https://docs.microsoft.com/dotnet/api/system.diagnostics.stacktrace.-ctor?view=netframework-4.7.1#System_Diagnostics_StackTrace__ctor_System_Boolean_) constructor with `false` argument to avoid capturing source information. This avoids the portion of the code where performance
 regressed.
 
 ## Resolution
-The fix for this issue is expected in a future servicing update. 
+
+[09-Jan-2018] The fix for this issue is included  in the [Update for .NET Framework 4.7.1 - KB4054856](http://go.microsoft.com/fwlink/?LinkId=866028) for all platforms except Windows 10 Fall Creators Update.
+
diff --git a/...ized on previous versions of .NET do not correctly deserialize on .NET 4.7.1.md b/...ized on previous versions of .NET do not correctly deserialize on .NET 4.7.1.md
@@ -21,8 +21,12 @@ P:System.StringComparer.CurrentCultureIgnoreCase
 
 Ensure that both serialization and deserialization occurs on systems running a version of the .NET Framework starting with 4.7.1.
 
+## Resolution
+
 If you are running on Windows 10 Fall Creators Update, an update is available that addresses this issue. Select one of the following links based on your processor architecture:
 
-x86: https://go.microsoft.com/fwlink/?linkid=862758
+    x86: https://go.microsoft.com/fwlink/?linkid=862758
+
+    x64: https://go.microsoft.com/fwlink/?linkid=862762
 
-x64: https://go.microsoft.com/fwlink/?linkid=862762
+[09-Jan-2018] The fix for this issue is included  in the [Update for .NET Framework 4.7.1 - KB4054856](http://go.microsoft.com/fwlink/?LinkId=866028) for all platforms except Windows 10 Fall Creators Update.