Add language identifiers to inline snippets (dotnet#176)

Author: ChrisMaddock

xml/Microsoft.Windows.Themes/SystemDropShadowChrome.xml

@@ -43,7 +43,7 @@
 <a name="xamlObjectElementUsage_SDSC"></a>   
 ## XAML Object Element Usage  
   
-```  
+```xaml  
 <theme:SystemDropShadowChrome ...>  
   singleChild  
 </theme:SystemDropShadowChrome>  

xml/System.Globalization/CultureAndRegionInfoBuilder.xml

@@ -329,8 +329,7 @@
   
  In the LDML file, the properties of a culture are specified as child elements of the `<special>` element in the `<identity>` section. A property value is typically specified by the element's `type` attribute. For example, the following excerpt from an LDML file defines a culture's parent as the English neutral culture.  
   
-```  
-  
+```xml  
 <identity>  
    <version number="1.1">ldml version 1.1</version>  
    <generation date="2012-05-16" />  
@@ -340,7 +339,6 @@
       <!—content removed -->  
    </special>  
 </identity>  
-  
 ```  
   
  For more information about the LDML standard, see  [Unicode Technical Standard #35, "Locale Data Markup Language (LDML)"](http://go.microsoft.com/fwlink/p/?LinkId=252840) on the Unicode Consortium website.  

xml/System.Globalization/CultureInfo.xml

@@ -1437,9 +1437,9 @@ greeting =Hello again!
 newGreeting=Hello!  
 ```  
   
- It is compiled to a binary .resources file named GreetingStrings.resources by using the  [Resource File Generator](~/docs/framework/tools/resgen-exe-resource-file-generator.md) with the following command.  
+ It is compiled to a binary .resources file named GreetingStrings.resources by using the [Resource File Generator](~/docs/framework/tools/resgen-exe-resource-file-generator.md) with the following command.  
   
-```  
+```console  
 resgen greetingstrings.txt  
 ```  
   
@@ -1450,27 +1450,27 @@ greeting=Еще раз привет!
 newGreeting=Привет!  
 ```  
   
- It is compiled to a binary .resources file named GreetingStrings.ru-RU.resources by using the  [Resource File Generator](~/docs/framework/tools/resgen-exe-resource-file-generator.md) with the following command.  
+ It is compiled to a binary .resources file named GreetingStrings.ru-RU.resources by using the [Resource File Generator](~/docs/framework/tools/resgen-exe-resource-file-generator.md) with the following command.  
   
-```  
+```console  
 resgen greetingstrings.ru-RU.txt  
 ```  
   
  The application code, which is shown below, resides in a file named Example1.vb or Example1.cs. It is compiled to an executable by using the following command for the Visual Basic compiler:  
   
-```  
+```console  
 vbc Example1.vb /resource:GreetingStrings.resources  
 ```  
   
  For the C# compiler, the command is similar:  
   
-```  
+```console  
 csc /resource:GreetingStrings.resources Example1.cs  
 ```  
   
- This creates an assembly that includes the example's executable code along with the resources for its fallback culture. You can also use the  [Assembly Linker](~/docs/framework/tools/al-exe-assembly-linker.md) to create the resource file for the Russian (Russia) culture with the following command:  
+ This creates an assembly that includes the example's executable code along with the resources for its fallback culture. You can also use the [Assembly Linker](~/docs/framework/tools/al-exe-assembly-linker.md) to create the resource file for the Russian (Russia) culture with the following command:  
   
-```  
+```console  
 >al /embed:greetingstrings.ru-RU.resources /c:ru-RU /template:example1.exe /out:ru-RU\Example1.resources.dll  
 ```  
   

xml/System.Net/Cookie.xml

@@ -140,15 +140,15 @@
   
  The `value` parameter for a <xref:System.Net.Cookie> must not be a `null` reference (Nothing in Visual Basic). The semicolon (";") and comma (",") characters are reserved and cannot be passed in the `value` parameter unless the string passed in the `value` parameter is enclosed in double quotes. So the following example constructor would succeed, but when you try to add this <xref:System.Net.Cookie> to a <xref:System.Net.CookieContainer> instance with the <xref:System.Net.CookieContainer.Add(System.Net.Cookie)> or <xref:System.Net.CookieContainer.Add(System.Uri,System.Net.Cookie)> methods, the operation will fail and throw an exception:  
   
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "123,456");
  cookie.Domain = "https://contoso.com";
  new CookieContainer().Add(cookie);
  ```  
   
  However, the following constructor with these special characters escaped will create a <xref:System.Net.Cookie> that can be added to a <xref:System.Net.CookieContainer> instance:  
  
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "\"123,456\"");
  cookie.Domain = "https://contoso.com";
  new CookieContainer().Add(cookie);
@@ -222,15 +222,15 @@
   
  The `value` parameter for a <xref:System.Net.Cookie> must not be a `null` reference (Nothing in Visual Basic). The semicolon (";") and comma (",") characters are reserved and cannot be passed in the `value` parameter unless the string passed in the `value` parameter is enclosed in double quotes. So the following example constructor would succeed, but when you try to add this <xref:System.Net.Cookie> to a <xref:System.Net.CookieContainer> instance with the <xref:System.Net.CookieContainer.Add(System.Net.Cookie)> or <xref:System.Net.CookieContainer.Add(System.Uri,System.Net.Cookie)> methods, the operation will fail and throw an exception:  
   
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "123,456", "");
  cookie.Domain = "https://contoso.com";
  new CookieContainer().Add(cookie);
  ```  
   
  However, the following constructor with these special characters escaped will create a <xref:System.Net.Cookie> that can be added to a <xref:System.Net.CookieContainer> instance:  
  
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "\"123,456\"", "");
  cookie.Domain = "https://contoso.com";
  new CookieContainer().Add(cookie);
@@ -306,14 +306,14 @@
   
  The `value` parameter for a <xref:System.Net.Cookie> must not be a `null` reference (Nothing in Visual Basic). The semicolon (";") and comma (",") characters are reserved and cannot be passed in the `value` parameter unless the string passed in the `value` parameter is enclosed in double quotes. So the following example constructor would succeed, but when you try to add this <xref:System.Net.Cookie> to a <xref:System.Net.CookieContainer> instance with the <xref:System.Net.CookieContainer.Add(System.Net.Cookie)> or <xref:System.Net.CookieContainer.Add(System.Uri,System.Net.Cookie)> methods, the operation will fail and throw an exception:  
   
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "123,456", "", "https://contoso.com");
  new CookieContainer().Add(cookie);
  ```  
   
  However, the following constructor with these special characters escaped will create a <xref:System.Net.Cookie> that can be added to a <xref:System.Net.CookieContainer> instance:  
  
- ```
+ ```csharp
  System.Net.Cookie cookie = new System.Net.Cookie("contoso", "\"123,456\"", "", "https://contoso.com");
  new CookieContainer().Add(cookie);
  ```  

xml/System.Net/WebClient.xml

@@ -1381,14 +1381,16 @@
 > [!NOTE]
 >  A passive FTP file transfer will always show a progress percentage of zero, since the server did not send the file size. To show progress, you can change the FTP connection to active by overriding the <xref:System.Net.WebClient.GetWebRequest%2A> virtual method:  
   
-```  
-internal class MyWebClient:WebClient{  
-        protected override WebRequest GetWebRequest(Uri address) {  
-            FtpWebRequest req = (FtpWebRequest)base.GetWebRequest(address);  
-            req.UsePassive = false;  
-            return req;  
-        }  
+```csharp  
+internal class MyWebClient : WebClient
+{  
+    protected override WebRequest GetWebRequest(Uri address)
+    {  
+        FtpWebRequest req = (FtpWebRequest)base.GetWebRequest(address);  
+        req.UsePassive = false;  
+        return req;  
     }  
+}  
 ```  
   
    

xml/System.Printing/PrintCapabilities.xml

@@ -450,7 +450,7 @@
 ## Examples  
  The following code example shows how to search for a particular value in the <xref:System.Printing.PrintCapabilities.PageMediaSizeCapability%2A>.  
   
-```  
+```csharp  
 foreach (PageMediaSize mediaSize in pc.PageMediaSizeCapability)  
     {  
         if (mediaSize.PageMediaSizeName == PageMediaSizeName.ISOA4)  
@@ -586,7 +586,7 @@ foreach (PageMediaSize mediaSize in pc.PageMediaSizeCapability)
 ## Examples  
  The following code example shows how to search for a particular value in the <xref:System.Printing.PrintCapabilities.PageResolutionCapability%2A>.  
   
-```  
+```csharp  
 foreach (PageResolution pageRes in pc.PageResolutionCapability)  
     {  
         if (pageRes.QualitativeResolution == PageQualitativeResolution.High)  

xml/System/Array.xml

@@ -5676,13 +5676,13 @@
 ## Remarks  
  For example, the Visual Basic code  
 
-```  
+```vb  
 Dim TDArray(0,0,0) As Integer  
 ```  
 
  and the C# code  
 
-```  
+```csharp  
 int[,,] TDArray = new int[1,1,1];  
 ```  
 

xml/System/CLSCompliantAttribute.xml

@@ -66,20 +66,20 @@
 ## Examples  
  The following example applies a <xref:System.CLSCompliantAttribute> to the entire assembly.  
   
-```  
+```csharp  
 using System;  
     [assembly: CLSCompliant(true)]  
 ```  
   
  The following declaration generates a CLS-compliance warning because the type `UInt32` is not specified in the CLS.  
   
-```  
+```csharp  
 public int SetValue(UInt32 value);  
 ```  
   
  If the declaration is marked with a <xref:System.CLSCompliantAttribute>, no compiler warning or error is generated.  
   
-```  
+```csharp  
 [CLSCompliant(false)]  
  public int SetValue(UInt32 value);  
 ```  

xml/System/NonSerializedAttribute.xml

@@ -47,7 +47,7 @@
   
  To apply the <xref:System.NonSerializedAttribute> class to an event, set the attribute location to field, as shown in the following C# code.  
   
-```  
+```csharp  
 [field:NonSerializedAttribute()]   
 public event ChangedEventHandler Changed;  
 ```  

xml/System/Object.xml

@@ -1031,13 +1031,13 @@ The scope of the <xref:System.Object.Finalize%2A?displayProperty=nameWithType> m
   
 -   You can define the [IStringable](http://msdn.microsoft.com/library/windows/apps/windows.foundation.istringable.aspx) interface only in a "class implements" relationship, such as  
   
-    ```  
+    ```csharp  
     public class NewClass : IStringable  
     ```  
   
      in C#, or  
   
-    ```  
+    ```vb  
     Public Class NewClass : Implements IStringable  
     ```  
   
@@ -1051,7 +1051,7 @@ The scope of the <xref:System.Object.Finalize%2A?displayProperty=nameWithType> m
   
 -   You cannot hide your [IStringable](http://msdn.microsoft.com/library/windows/apps/windows.foundation.istringable.aspx) implementation from base classes by using a method definition such as the following:  
   
-    ```  
+    ```csharp  
   
     public class NewClass : IStringable  
     {