Add code types to snippets (dotnet#167)

Author: ChrisMaddock

xml/System.Xml/IFragmentCapableXmlDictionaryWriter.xml

@@ -1,4 +1,4 @@
-<Type Name="IFragmentCapableXmlDictionaryWriter" FullName="System.Xml.IFragmentCapableXmlDictionaryWriter">
+<Type Name="IFragmentCapableXmlDictionaryWriter" FullName="System.Xml.IFragmentCapableXmlDictionaryWriter">
   <TypeSignature Language="C#" Value="public interface IFragmentCapableXmlDictionaryWriter" />
   <TypeSignature Language="ILAsm" Value=".class public interface auto ansi abstract IFragmentCapableXmlDictionaryWriter" />
   <TypeSignature Language="DocId" Value="T:System.Xml.IFragmentCapableXmlDictionaryWriter" />
@@ -191,7 +191,7 @@
   
 ## Examples  
   
-```  
+```csharp  
 MemoryStream stream = new MemoryStream();  
 MemoryStream fragmentStream = new MemoryStream();  
 XmlDictionaryWriter writer = XmlDictionaryWriter.CreateTextWriter(stream);  

xml/System.Xml/IHasXmlNode.xml

@@ -1,4 +1,4 @@
-<Type Name="IHasXmlNode" FullName="System.Xml.IHasXmlNode">
+<Type Name="IHasXmlNode" FullName="System.Xml.IHasXmlNode">
   <TypeSignature Language="C#" Value="public interface IHasXmlNode" />
   <TypeSignature Language="ILAsm" Value=".class public interface auto ansi abstract IHasXmlNode" />
   <TypeSignature Language="DocId" Value="T:System.Xml.IHasXmlNode" />
@@ -78,7 +78,7 @@
 ## Remarks  
  The following C# code uses `GetNode` to access a node the <xref:System.Xml.XPath.XPathNavigator> is currently positioned on.  
   
-```  
+```csharp  
 XmlDocument doc = new XmlDocument();  
 doc.Load("books.xml");  
 XPathNavigator nav =  doc.CreateNavigator();  

xml/System.Xml/XmlConvert.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlConvert" FullName="System.Xml.XmlConvert">
+<Type Name="XmlConvert" FullName="System.Xml.XmlConvert">
   <TypeSignature Language="C#" Value="public class XmlConvert" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit XmlConvert extends System.Object" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlConvert" />
@@ -40,7 +40,7 @@
   
  You can use the <xref:System.Xml.XmlConvert.EncodeName%2A> method with the <xref:System.Xml.XmlWriter> class to ensure the names being written are valid XML names. The following C# code converts the name "Order Detail" into a valid XML name and writes the element `<Order_0x0020_Detail>My order</Order_0x0020_Detail>`.  
   
-```  
+```csharp  
 writer.WriteElementString(XmlConvert.EncodeName("Order Detail"),"My order");  
   
 ```  
@@ -964,7 +964,7 @@ writer.WriteElementString(XmlConvert.EncodeName("Order Detail"),"My order");
   
  The example uses the transactions.xml file.  
   
-```  
+```xml  
 <?xml version="1.0"?>  
 <transactions>  
    <transaction>  
@@ -1038,7 +1038,7 @@ writer.WriteElementString(XmlConvert.EncodeName("Order Detail"),"My order");
   
  The example uses the transactions.xml file.  
   
-```  
+```xml  
 <?xml version="1.0"?>  
 <transactions>  
    <transaction>  
@@ -1112,7 +1112,7 @@ writer.WriteElementString(XmlConvert.EncodeName("Order Detail"),"My order");
   
  The example uses the transactions.xml file.  
   
-```  
+```xml  
 <?xml version="1.0"?>  
 <transactions>  
    <transaction>  
@@ -2579,7 +2579,7 @@ writer.WriteElementString(XmlConvert.EncodeName("Order Detail"),"My order");
 ## Remarks  
  This method can be used with the <xref:System.Xml.XmlWriter> class in the following manner.  
   
-```  
+```csharp  
 try{  
   writer.WriteStartElement(XmlConvert.VerifyName("item"),"bar");  
 }  
@@ -2688,7 +2688,7 @@ catch(Exception e)
 ## Remarks  
  This method ensures that the name token follows the proper syntax for a valid NMTOKEN. It can be used in the following manner:  
   
-```  
+```csharp  
 try {  
   writer.WriteStartElement(XmlConvert.VerifyNMTOKEN("abc"),"book");  
 }  
@@ -2792,7 +2792,7 @@ catch(Exception e) {
 ## Remarks  
  This method ensures that the name token follows the proper syntax for a valid token. It can be used in the following manner:  
   
-```  
+```csharp  
 try {  
   writer.WriteStartElement(XmlConvert.VerifyTOKEN("abc"),"book");  
 }  

xml/System.Xml/XmlDataDocument.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlDataDocument" FullName="System.Xml.XmlDataDocument">
+<Type Name="XmlDataDocument" FullName="System.Xml.XmlDataDocument">
   <TypeSignature Language="C#" Value="public class XmlDataDocument : System.Xml.XmlDocument" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit XmlDataDocument extends System.Xml.XmlDocument" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlDataDocument" />
@@ -193,7 +193,7 @@
 ## Remarks  
  `Note to Inheritors` If you overload this function, it cannot be used for extensibility. Instead, you can return an element created by the base class, in this case, `XmlDataDocument`. See the following example.  
   
-```  
+```csharp  
 class MyXmlDataDocument : XmlDataDocument {  
  public override XmlElement CreateElement(string prefix, string localName, string nsURI) {  
    //Ensure we are returning the base class implementation of element.  
@@ -640,13 +640,13 @@ class MyXmlDataDocument : XmlDataDocument {
   
  If the current node and its following siblings look similar to the following:  
   
-```  
+```xml  
 <!--comment--><element1>one</element1><element2>two</element2>  
 ```  
   
  `Load` throws an exception, because a document cannot have two root-level elements. If the current node and its following siblings look similar to the following:  
   
-```  
+```xml  
 <!--comment--><?process  
     instruction?><!--comment--></endtag>  
 ```  

xml/System.Xml/XmlDictionaryWriter.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlDictionaryWriter" FullName="System.Xml.XmlDictionaryWriter">
+<Type Name="XmlDictionaryWriter" FullName="System.Xml.XmlDictionaryWriter">
   <TypeSignature Language="C#" Value="public abstract class XmlDictionaryWriter : System.Xml.XmlWriter" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi abstract beforefieldinit XmlDictionaryWriter extends System.Xml.XmlWriter" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlDictionaryWriter" />
@@ -124,7 +124,7 @@
 ## Remarks  
  The binary format only supports one text node as the attribute value and therefore buffers the values written to it to emit a single node, as shown in the following sample code.  
   
-```  
+```csharp  
 XmlWriter binarywriter = XmlDictionaryWriter.CreateBinaryWriter(Stream.Null);  
 binarywriter.WriteStartAttribute("StartAttribute");  
 string largeStr = new string('r', 100000);  

xml/System.Xml/XmlDocument.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlDocument" FullName="System.Xml.XmlDocument">
+<Type Name="XmlDocument" FullName="System.Xml.XmlDocument">
   <TypeSignature Language="C#" Value="public class XmlDocument : System.Xml.XmlNode" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit XmlDocument extends System.Xml.XmlNode" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlDocument" />
@@ -1062,7 +1062,7 @@
 ## Remarks  
  The following C# code  
   
-```  
+```csharp  
 XmlElement elem;  
 elem=doc.CreateElement("xy:item", "urn:abc");  
 ```  
@@ -1127,7 +1127,7 @@ elem=doc.CreateElement("xy:item", "urn:abc");
 ## Remarks  
  The following C# code  
   
-```  
+```csharp  
 XmlElement elem;  
 elem=doc.CreateElement("xy", "item", "urn:abc");  
 ```  
@@ -2412,7 +2412,7 @@ elem=doc.CreateElement("xy", "item", "urn:abc");
   
  `InnerXml` removes redundant namespace declarations. As a result, numerous cut and paste operations do not increase the size of your document with redundant namespace declarations. Consider the following XSL document:  
   
-```  
+```xml  
 <xsl:stylesheet version="1.0"   
       xmlns:xsl="http://www.w3.org/1999/XSL/Transform">  
      <xsl:template match="stock">  
@@ -2423,7 +2423,7 @@ elem=doc.CreateElement("xy", "item", "urn:abc");
   
  The `InnerXml` property on the stylesheet node returns the following string:  
   
-```  
+```xml  
 <xsl:template match="stock"   
       xmlns:xsl="http://www.w3.org/1999/XSL/Transform">  
      ...  
@@ -2434,42 +2434,42 @@ elem=doc.CreateElement("xy", "item", "urn:abc");
   
  If you move `InnerXml` from a document with no default namespace to a document with a default namespace, the behavior is a little different. Consider the following XML string:  
   
-```  
+```xml  
 <test>  
       <item>123</item>  
     </test>  
 ```  
   
  `InnerXml` returns a plain XML string with no namespace declarations:  
   
-```  
+```xml  
 <item>123</item>  
 ```  
   
  If you then insert this string into a document that does have a default namespace, such as the following:  
   
-```  
+```xml  
 <test2 xmlns="urn:1">  
     </test>  
 ```  
   
  `InnerXml` parses the string in context, and the new nodes pick up the urn:1 namespace. The result looks like this:  
   
-```  
+```xml  
 <test2 xmlns="urn:1">  
       <item>123</item>  
     </test>  
 ```  
   
  Now when you ask for the `InnerXml` you get back the following:  
   
-```  
+```xml  
 <item xmlns="urn:1">123</item>  
 ```  
   
  If you explicitly want the inserted item to preserve the fact that it came from a document that had no namespace then you need to manually add an xmlns= "" declaration and insert the resulting string:  
   
-```  
+```xml  
 <item xmlns="">123</item>  
 ```  
   
@@ -2797,13 +2797,13 @@ elem=doc.CreateElement("xy", "item", "urn:abc");
   
  If the current node and its siblings look like the following:  
   
-```  
+```xml  
 <!--comment--><element1>one</element1><element2>two</element2>  
 ```  
   
  `Load` throws an exception because a document cannot have two root level elements. If the current node and its siblings look like the following:  
   
-```  
+```xml  
 <!--comment--><?process instruction?><!--comment--></endtag>  
 ```  
   
@@ -3488,7 +3488,7 @@ elem=doc.CreateElement("xy", "item", "urn:abc");
   
  `ReadNode` can also read attributes, but in this case it does not advance the reader to the next attribute. This allows you to write the following C# code:  
   
-```  
+```csharp  
 XmlDocument doc = new XmlDocument();  
 while (reader.MoveToNextAttribute())  
 {  
@@ -3577,7 +3577,7 @@ while (reader.MoveToNextAttribute())
   
  When the document is saved, xmlns attributes are generated to persist the node identity (local name + namespace URI) correctly. For example, the following C# code  
   
-```  
+```csharp  
 XmlDocument doc = new XmlDocument();  
 doc.AppendChild(doc.CreateElement("item","urn:1"));  
 doc.Save(Console.Out);  
@@ -3683,7 +3683,7 @@ doc.Save(Console.Out);
   
  When the document is saved, xmlns attributes are generated to persist the node identity (local name + namespace URI) correctly. For example, the following C# code  
   
-```  
+```csharp  
 XmlDocument doc = new XmlDocument();  
 doc.AppendChild(doc.CreateElement("item","urn:1"));  
 doc.Save(Console.Out);  
@@ -3755,15 +3755,15 @@ doc.Save(Console.Out);
   
  When the document is saved, xmlns attributes are generated to persist the node identity (LocalName + NamespaceURI) correctly. For example, the following C# code  
   
-```  
+```csharp  
 XmlDocument doc = new XmlDocument();  
 doc.AppendChild(doc.CreateElement("item","urn:1"));  
 doc.Save(Console.Out);  
 ```  
   
  generates this xmls attribute:  
   
-```  
+```xml  
 <item  
     xmls="urn:1"/>  
 ```  

xml/System.Xml/XmlEntity.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlEntity" FullName="System.Xml.XmlEntity">
+<Type Name="XmlEntity" FullName="System.Xml.XmlEntity">
   <TypeSignature Language="C#" Value="public class XmlEntity : System.Xml.XmlNode" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit XmlEntity extends System.Xml.XmlNode" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlEntity" />
@@ -63,7 +63,7 @@
   
  The value of this property varies depending on the node type. Nodes which are children of external EntityReference nodes return the location of the entity itself. For example, consider the following XML document:  
   
-```  
+```xml  
 <!DOCTYPE item [  
 <!ENTITY xyz SYSTEM "a/b.xml">  
 ]>  
@@ -89,7 +89,7 @@
   
  As a second example, given the following XML document:  
   
-```  
+```xml  
 <!DOCTYPE Mydata SYSTEM "http://localhost/doctype.dtd">  
 <baa>&xyz;</baa>  
 ```  

xml/System.Xml/XmlNamespaceManager.xml

@@ -1,4 +1,4 @@
-<Type Name="XmlNamespaceManager" FullName="System.Xml.XmlNamespaceManager">
+<Type Name="XmlNamespaceManager" FullName="System.Xml.XmlNamespaceManager">
   <TypeSignature Language="C#" Value="public class XmlNamespaceManager : System.Collections.IEnumerable, System.Xml.IXmlNamespaceResolver" />
   <TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit XmlNamespaceManager extends System.Object implements class System.Collections.IEnumerable, class System.Xml.IXmlNamespaceResolver" />
   <TypeSignature Language="DocId" Value="T:System.Xml.XmlNamespaceManager" />
@@ -337,7 +337,7 @@ while (reader.Read())
 ## Remarks  
  The following code shows how to use the <xref:System.Collections.IEnumerator> to view all the namespace pairs stored in the <xref:System.Xml.XmlNamespaceManager> object.  
   
-```  
+```vb  
 Dim nsEnum As IEnumerator = nsmgr.GetEnumerator()  
 Do While nsEnum.MoveNext  
   If nsEnum.Current <> "" Then