fix non-working sample (#4765)

Author: mairaw

samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.numberformatinfo.class/cs/parsepersisted.cs

@@ -9,10 +9,10 @@ public class Example
 {
    public static void Main()
    {
-      Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("en-US");
+      CultureInfo.CurrentCulture = CultureInfo.CreateSpecificCulture("en-US");
       PersistData();
 
-      Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("en-GB");
+      CultureInfo.CurrentCulture = CultureInfo.CreateSpecificCulture("pt-BR");
       RestoreData();
    }
 

samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.numberformatinfo.class/vb/parsepersisted.vb

@@ -9,10 +9,10 @@ Imports System.Threading
 
 Module Example
    Public Sub Main()
-      Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("en-US")
+      CultureInfo.CurrentCulture = CultureInfo.CreateSpecificCulture("en-US")
       PersistData()
 
-      Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("en-GB")
+      CultureInfo.CurrentCulture = CultureInfo.CreateSpecificCulture("pt-BR")
       RestoreData()
    End Sub
 

xml/System.Globalization/NumberFormatInfo.xml

@@ -333,7 +333,9 @@
 ### Serializing and deserializing numeric data  
  When numeric data is serialized in string format and later deserialized and parsed, the strings should be generated and parsed by using the conventions of the invariant culture. The formatting and parsing operations should never reflect the conventions of a specific culture. If culture-specific settings are used, the portability of the data is strictly limited; it can be successfully deserialized only on a thread whose culture-specific settings are identical to those of the thread on which it was serialized. In some cases, this means that the data cannot even be successfully deserialized on the same system on which it was serialized.  
   
- The following example illustrates what can happen when this principle is violated. Floating-point values in an array are converted to strings when the current thread uses the culture-specific settings of the en-US culture. The data is then parsed by a thread that uses the culture-specific settings of the en-GB culture. In this case, although each parsing operation succeeds, the data does not round-trip successfully and data corruption occurs. In other cases, a parsing operation could fail and a <xref:System.FormatException> exception could be thrown.  
+ The following example illustrates what can happen when this principle is violated. Floating-point values in an array are converted to strings when the current thread uses the culture-specific settings of the en-US culture. 
+ The data is then parsed by a thread that uses the culture-specific settings of the pt-BR culture. In this case, although each parsing operation succeeds, the data doesn't round-trip successfully and data corruption occurs. 
+ In other cases, a parsing operation could fail and a <xref:System.FormatException> exception could be thrown.  
   
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.numberformatinfo.class/cs/parsepersisted.cs" interactive="try-dotnet" id="Snippet6"::: 
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.numberformatinfo.class/vb/parsepersisted.vb" id="Snippet6":::