4.7.2 known issue for visualstylestate (microsoft#921)

dreddy-work · Ron Petrusha · commit 29bbcba0b336 · 2018-11-14T14:16:43.000-08:00
* 4.7.2 known issue for visualstylestate

* resolving comments

* resolving comment

* Resolving comments that were missed.

* Deletign duplicate file.

* Update 706819 - Winforms applications may have problems rendering UI on latest Operating Systems.md
diff --git a/releases/net472/KnownIssues/706819 - Winforms applications may have problems rendering UI on latest Operating Systems.md b/releases/net472/KnownIssues/706819 - Winforms applications may have problems rendering UI on latest Operating Systems.md
@@ -0,0 +1,10 @@
+ # WinForms applications may have problems rendering the application UI and instead may render a white screen with a red ‘X’ symbol. The issue is caused by a change in Windows 10 October 2018 Update that exposed a bug in .NET Framework 4.7.2.
+
+## Symptoms
+WinForms applications may have problems rendering the application UI and instead may render a white screen with a red ‘X’ symbol. The issue is caused by a change in Windows 10 October 2018 Update that exposed a bug in .NET Framework 4.7.2.
+
+## Cause
+The issue is caused by a change in Windows 10 October 2018 Update that exposed a bug in .NET Framework 4.7.2. The Windows 10 October 2018 Update adds a new flag to VisualStyle state when the application UI launches a child  dialog (i.e., a FileSaveDialog or PrintpreviewDialog) that causes .NET Framework to fail its VisualStyleState check and thus throw an exception while rendering the application UI.
+
+## Resolution
+A .NET 4.7.2 servicing fix for this will be released in near future and will also be included in the next version (4.8) of .NET Framework. This known issue will be updated with more details when that happens.
diff --git a/releases/net472/dotnet472-known-issues.md b/releases/net472/dotnet472-known-issues.md
@@ -14,4 +14,5 @@ This document lists the known issues that you may experience after you install t
 - [613745 - BCL - Single-name references are removed by the SDK when targeting 4.7.2](https://github.com/Microsoft/dotnet/blob/master/releases/net472/KnownIssues/613745%20-%20Single-name%20references%20are%20removed%20by%20the%20SDK%20when%20targeting%204.7.2.md)
 - [663475 - Setup - Applications that rely on TLS 1.2 strong encryption experience connectivity failures after a Windows upgrade](https://support.microsoft.com/help/4458166)
 - [669153 - Remoting calls made within a transaction can lead to Transaction.Current incorrectly returning null](https://github.com/Microsoft/dotnet/blob/master/releases/net472/KnownIssues/669153%20-%20Remoting%20calls%20made%20within%20a%20transaction%20can%20lead%20to%20Transaction.Current%20incorrectly%20returning%20null.md)
-- [695400 - Setup fails to install the product after migrating OS from Windows 7 or Windows Server 2008 R2](https://github.com/Microsoft/dotnet/blob/master/releases/net472/KnownIssues/695400%20-%20Setup%20fails%20to%20install%20the%20product%20after%20migrating%20OS%20from%20Windows%207%20or%20Windows%20Server%202008%20R2.md)
+- [695400 - Setup fails to install the product after migrating OS from Windows 7 or Windows Server 2008 R2](https://github.com/Microsoft/dotnet/blob/master/releases/net472/KnownIssues/695400%20-%20Setup%20fails%20to%20install%20the%20product%20after%20migrating%20OS%20from%20Windows%207%20or%20Windows%20Server%202008%20R2.md)
+- [706819 - Winforms applications may have problems rendering UI on latest Windows operating system] (https://github.com/Microsoft/dotnet/blob/master/releases/net472/KnownIssues/706819%20-%20Winforms%20applications%20may%20have%20problems%20rendering%20UI%20on%20latest%20Windows%20operating%20system.md)
