Add lang identifiers (dotnet#169)

Author: ChrisMaddock

xml/System.Diagnostics/BooleanSwitch.xml

@@ -40,7 +40,7 @@
   
  To configure a <xref:System.Diagnostics.BooleanSwitch>, edit the configuration file that corresponds to the name of your application. Within this file, you can add or remove a switch, set a switch's value, or clear all the switches previously set by the application. The configuration file should be formatted like the following example.  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <switches>  
@@ -137,7 +137,7 @@
   
  To set the level of your <xref:System.Diagnostics.BooleanSwitch>, edit the configuration file corresponding to the name of your application. Within this file, you can add a switch and set its value, remove a switch, or clear all switches previously set by the application. The configuration file should be formatted like the following example:  
   
-```  
+```xml  
 <configuration>  
     <system.diagnostics>  
        <switches>  

xml/System.Diagnostics/ConsoleTraceListener.xml

@@ -47,7 +47,7 @@
   
  The following example adds a <xref:System.Diagnostics.ConsoleTraceListener> object named `configConsoleListener` to the <xref:System.Diagnostics.Trace.Listeners%2A> collection.  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="false" indentsize="4">  

xml/System.Diagnostics/Debug.xml

@@ -45,7 +45,7 @@
   
  To set the <xref:System.Diagnostics.Debug.AutoFlush%2A> and <xref:System.Diagnostics.Debug.IndentSize%2A> for <xref:System.Diagnostics.Debug>, you can edit the configuration file corresponding to the name of your application. The configuration file should be formatted as shown in the following example.  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="true" indentsize="7" />  
@@ -153,7 +153,7 @@
   
  You can change the behavior of the <xref:System.Diagnostics.DefaultTraceListener> in the configuration file that corresponds to the name of your application. In this file, you can enable and disable the assert message box or set the <xref:System.Diagnostics.DefaultTraceListener.LogFileName%2A?displayProperty=nameWithType> property. The configuration file should be formatted as follows:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <assert assertuienabled="true" logfilename="c:\\myFile.log" />  
@@ -236,7 +236,7 @@
   
  You can change the behavior of the <xref:System.Diagnostics.DefaultTraceListener> in the configuration file that corresponds to the name of your application. In this file, you can enable and disable the assert message box or set the <xref:System.Diagnostics.DefaultTraceListener.LogFileName%2A?displayProperty=nameWithType> property. The configuration file should be formatted as follows:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <assert assertuienabled="true" logfilename="c:\\myFile.log" />  
@@ -320,7 +320,7 @@
   
  You can change the behavior of the <xref:System.Diagnostics.DefaultTraceListener> in the configuration file that corresponds to the name of your application. In this file, you can enable and disable the assert message box or set the <xref:System.Diagnostics.DefaultTraceListener.LogFileName%2A?displayProperty=nameWithType> property. The configuration file should be formatted as follows:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <assert assertuienabled="true" logfilename="c:\\myFile.log" />  
@@ -414,7 +414,7 @@
   
  You can change the behavior of the <xref:System.Diagnostics.DefaultTraceListener> in the configuration file that corresponds to the name of your application. In this file, you can enable and disable the assert message box or set the <xref:System.Diagnostics.DefaultTraceListener.LogFileName%2A?displayProperty=nameWithType> property. The configuration file should be formatted as follows:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <assert assertuienabled="true" logfilename="c:\\myFile.log" />  
@@ -464,7 +464,7 @@
   
  To set the <xref:System.Diagnostics.Debug.AutoFlush%2A> and <xref:System.Diagnostics.Debug.IndentSize%2A> for <xref:System.Diagnostics.Debug>, you can also edit the configuration file corresponding to the name of your application. The configuration file should be formatted as shown in the following example.  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="true" indentsize="7" />  
@@ -927,7 +927,7 @@ End of list of errors
   
  To set the <xref:System.Diagnostics.Debug.AutoFlush%2A> and <xref:System.Diagnostics.Debug.IndentSize%2A> for <xref:System.Diagnostics.Debug>, you can also edit the configuration file corresponding to the name of your application. The configuration file should be formatted as shown in the following example.  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="true" indentsize="7" />  
@@ -1543,14 +1543,14 @@ End of list of errors
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.Write("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -1630,14 +1630,14 @@ Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.Write("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -1721,14 +1721,14 @@ Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.Write("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -1812,14 +1812,14 @@ Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.Write("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -2267,14 +2267,14 @@ Debug.WriteIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.WriteLine("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -2355,14 +2355,14 @@ Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range")
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.WriteLine("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -2446,14 +2446,14 @@ Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range")
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.WriteLine("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>
@@ -2538,14 +2538,14 @@ Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range")
 
  First example:  
 
-```  
+```csharp  
 if(mySwitch.TraceError)   
     Debug.WriteLine("aNumber = " + aNumber + " out of range");  
 ```  
 
  Second example:  
 
-```  
+```csharp  
 Debug.WriteLineIf(mySwitch.TraceError, "aNumber = " + aNumber + " out of range");  
 ```</para>
         </block>

xml/System.Diagnostics/DebuggerDisplayAttribute.xml

@@ -40,7 +40,7 @@
 ## Remarks  
  The <xref:System.Diagnostics.DebuggerDisplayAttribute.%23ctor%2A> constructor has a single argument: a string to be displayed in the value column for instances of the type. This string can contain braces ({ and }). The text within a pair of braces is evaluated as the name of a field, property, or method. For example, the following C# code causes "Count = 4" to be displayed when the plus sign (+) is selected to expand the debugger display for an instance of `MyHashtable`.  
   
-```  
+```csharp  
 [DebuggerDisplay("Count = {count}")]  
 class MyHashtable  
 {  
@@ -98,7 +98,7 @@ class MyHashtable
 ## Remarks  
  The `value` parameter can contain braces ({ and }). The text within a pair of braces is evaluated as the name of a field, property, or method. For example, the following C# code causes "Count = 4" to be displayed when the plus sign (+) is selected to expand the debugger display for an instance of `MyTable`.  
   
-```  
+```csharp  
 [DebuggerDisplay("Count = {count}")]  
 class MyTable  
 {  

xml/System.Diagnostics/DebuggerNonUserCodeAttribute.xml

@@ -50,7 +50,7 @@
 ## Examples  
  The following code example shows the use of this attribute in a Visual Basic project.  
   
-```  
+```vb  
 ' Form overrides Dispose to clean up the component list.  
 <System.Diagnostics.DebuggerNonUserCode()> _  
 Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)  

xml/System.Diagnostics/DebuggerStepThroughAttribute.xml

@@ -48,7 +48,7 @@
   
  The following code shows how the Visual Basic compiler uses the attribute.  
   
-```  
+```vb  
 <System.Diagnostics.DebuggerStepThrough()> _  
     Private Sub InitializeComponent()  
         components = New System.ComponentModel.Container()  

xml/System.Diagnostics/DefaultTraceListener.xml

@@ -46,7 +46,7 @@
   
  To add a trace listener, edit the configuration file that corresponds to the name of your application. Within this file, you can add a listener, set its type and set its parameters, remove a listener, or clear all the listeners previously set by the application. The configuration file should be formatted similar to the following example:  
   
-```  
+```xml  
 <configuration>  
 <system.diagnostics>  
   <trace autoflush="false" indentsize="4">  

xml/System.Diagnostics/DelimitedListTraceListener.xml

@@ -41,7 +41,7 @@
   
  To configure a <xref:System.Diagnostics.DelimitedListTraceListener>, edit the configuration file that corresponds to the name of your application. In this file, you can add a listener, set the properties for a listener, or remove a listener. The configuration file should be formatted as shown in the following example:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="false" indentsize="4">  
@@ -230,7 +230,7 @@
 ## Remarks  
  This constructor initializes the <xref:System.Diagnostics.TraceListener.Name%2A> property to the value of the `name` parameter, or to an empty string ("") if the `name` parameter is `null`.  The <xref:System.Diagnostics.TraceListener.Name%2A> property can be used as an index into the `Listeners` collection to programmatically change the properties for the listener. For example, the following code sets the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property for the instance of <xref:System.Diagnostics.DelimitedListTraceListener> that has the name "delimListener":  
   
-```  
+```csharp  
 ((DelimitedListTraceListener)Trace.Listeners["delimListener"]).Delimiter = ":"  
 ```  
   
@@ -276,7 +276,7 @@
 ## Remarks  
  This constructor initializes the <xref:System.Diagnostics.TraceListener.Name%2A> property to the value of the `name` parameter, or to an empty string ("") if the `name` parameter is `null`. The <xref:System.Diagnostics.TraceListener.Name%2A> property can be used as an index into the `Listeners` collection to programmatically change the properties for the listener. For example the following code sets the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property for the instance of <xref:System.Diagnostics.DelimitedListTraceListener> that has the name "delimListener":  
   
-```  
+```csharp  
 ((DelimitedListTraceListener)Trace.Listeners["delimListener"]).Delimiter = ":"  
 ```  
   
@@ -326,7 +326,7 @@
   
  The <xref:System.Diagnostics.TraceListener.Name%2A> property is set to the value of the `name` parameter, or to an empty string ("") if the `name` parameter is `null`. The <xref:System.Diagnostics.TraceListener.Name%2A> property can be used as an index into the `Listeners` collection to programmatically change the properties for the listener. For example, the following code sets the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property for the instance of <xref:System.Diagnostics.DelimitedListTraceListener> that has the name "delimListener":  
   
-```  
+```csharp  
 ((DelimitedListTraceListener)Trace.Listeners["delimListener"]).Delimiter = ":"  
 ```  
   
@@ -370,7 +370,7 @@
 ## Remarks  
  The default delimiter is ";" (semicolon). The following configuration file example shows the setting of the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property using the `delimiter` attribute in a configuration file:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="false" indentsize="4">  
@@ -430,7 +430,7 @@
 ## Remarks  
  A custom attribute is an attribute that is not inherited from the base class that can be used to set a property for the class. The custom attribute for <xref:System.Diagnostics.DelimitedListTraceListener> is used to set the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property. The following configuration file example shows the use of the `delimiter` attribute to set the <xref:System.Diagnostics.DelimitedListTraceListener.Delimiter%2A> property:  
   
-```  
+```xml  
 <configuration>  
   <system.diagnostics>  
     <trace autoflush="false" indentsize="4">  

xml/System.Diagnostics/EventSchemaTraceListener.xml

@@ -28,7 +28,7 @@
   
  To configure an <xref:System.Diagnostics.EventSchemaTraceListener> object, modify the configuration file that corresponds to the name of your application. In this file, you can add, remove, or set the properties for a listener. The configuration file should be formatted as follows:  
   
-```  
+```xml  
 <configuration>  
     <system.diagnostics>  
         <sources>  

xml/System.Diagnostics/Process.xml

@@ -454,7 +454,7 @@
   
  When you call <xref:System.Diagnostics.Process.CancelErrorRead%2A>, all in-progress read operations for <xref:System.Diagnostics.Process.StandardError%2A> are completed and then the event handler is disabled. All further redirected output to <xref:System.Diagnostics.Process.StandardError%2A> is saved in a buffer. If you re-enable the event handler with a call to <xref:System.Diagnostics.Process.BeginErrorReadLine%2A>, the saved output is sent to the event handler and asynchronous read operations resume. If you want to change the event handler before resuming asynchronous read operations, you must remove the existing event handler before adding the new event handler:  
   
-```  
+```csharp  
 // At this point the DataReceivedEventHandler(ErrorHandler1)   
 // has executed a CancelErrorRead.  
   
@@ -536,7 +536,7 @@ process.BeginErrorReadLine();
   
  When you call <xref:System.Diagnostics.Process.CancelOutputRead%2A>, all in-progress read operations for <xref:System.Diagnostics.Process.StandardOutput%2A> are completed and then the event handler is disabled. All further redirected output to <xref:System.Diagnostics.Process.StandardOutput%2A> is saved in a buffer. If you re-enable the event handler with a call to <xref:System.Diagnostics.Process.BeginOutputReadLine%2A>, the saved output is sent to the event handler and asynchronous read operations resume. If you want to change the event handler before resuming asynchronous read operations, you must remove the existing event handler before adding the new event handler:  
   
-```  
+```csharp  
 // At this point the DataReceivedEventHandler(OutputHandler1)   
 // has executed a CancelOutputRead.  
   
@@ -3944,7 +3944,7 @@ The following code example creates a process that prints a file. It sets the <xr
   
  The following C# code, for example, shows how to read from a redirected stream and wait for the child process to exit.  
   
-```  
+```csharp  
 // Start the child process.  
  Process p = new Process();  
  // Redirect the error stream of the child process.  
@@ -3964,7 +3964,7 @@ The following code example creates a process that prints a file. It sets the <xr
   
  There is a similar issue when you read all text from both the standard output and standard error streams. The following C# code, for example, performs a read operation on both streams.  
   
-```  
+```csharp  
 // Do not perform a synchronous read to the end of both   
 // redirected streams.  
 // string output = p.StandardOutput.ReadToEnd();  
@@ -4127,7 +4127,7 @@ p.WaitForExit();
   
  The following C# code, for example, shows how to read from a redirected stream and wait for the child process to exit.  
   
-```  
+```csharp  
 Process p = new Process();  
 p.StartInfo.UseShellExecute = false;  
 p.StartInfo.RedirectStandardOutput = true;  
@@ -4143,7 +4143,7 @@ p.WaitForExit();
   
  There is a similar issue when you read all text from both the standard output and standard error streams. The following C# code, for example, performs a read operation on both streams.  
   
-```  
+```csharp  
 // To avoid deadlocks, use asynchronous read operations on at least one of the streams.  
 // Do not perform a synchronous read to the end of both redirected streams.  
 p.BeginOutputReadLine();