labelling code blocks

Author: WilliamAntonRohm

docs/deployment/assembly-element-clickonce-application.md

@@ -24,7 +24,7 @@ The top-level element for the application manifest.
 
 ## Syntax  
 
-```  
+```xml  
 
       <assembly  
    manifestVersion  
@@ -51,7 +51,7 @@ The top-level element for the application manifest.
 ## Example  
  The following code example illustrates an `assembly` element in an application manifest for a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application. This code example is part of a larger example provided in [ClickOnce application manifest](../deployment/clickonce-application-manifest.md).  
 
-```  
+```xml
 <asmv1:assembly   
   xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd"   
   manifestVersion="1.0"   

docs/deployment/assemblyidentity-element-clickonce-application.md

@@ -24,7 +24,7 @@ Identifies the application deployed in a [!INCLUDE[ndptecclick](../deployment/in
 
 ## Syntax  
 
-```  
+```xml
 
       <assemblyIdentity   
    name  
@@ -53,7 +53,7 @@ Identifies the application deployed in a [!INCLUDE[ndptecclick](../deployment/in
 
 ### Code  
 
-```  
+```xml  
 <asmv1:assemblyIdentity   
   name="My Application Deployment.exe"   
   version="1.0.0.0"   

docs/deployment/assemblyidentity-element-clickonce-deployment.md

@@ -24,7 +24,7 @@ Identifies the primary assembly of the [!INCLUDE[ndptecclick](../deployment/incl
 
 ## Syntax  
 
-```  
+```xml  
 
       <assemblyIdentity    
    name   
@@ -51,7 +51,7 @@ Identifies the primary assembly of the [!INCLUDE[ndptecclick](../deployment/incl
 ## Example  
  The following code example illustrates an `assemblyIdentity` element in a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment manifest. This code example is part of a larger example provided for the [ClickOnce deployment manifest](../deployment/clickonce-deployment-manifest.md) topic.  
 
-```  
+```xml  
 <!-- Identify the deployment. -->  
 <assemblyIdentity   
   name="My Application Deployment.app"  

docs/deployment/building-clickonce-applications-from-the-command-line.md

@@ -76,7 +76,7 @@ In [!INCLUDE[vs_current_short](../code-quality/includes/vs_current_short_md.md)]
 
  In *CmdLineDemo.vbproj* / *CmdLineDemo.csproj*:  
 
-```  
+```xml  
 <AssemblyOriginatorKeyFile>WindowsApplication3.snk</AssemblyOriginatorKeyFile>  
 <GenerateManifests>true</GenerateManifests>  
 <TargetZone>LocalIntranet</TargetZone>  
@@ -98,7 +98,7 @@ In [!INCLUDE[vs_current_short](../code-quality/includes/vs_current_short_md.md)]
 
  You can override any of these properties at the command line without altering the project file itself. For example, the following will build the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application deployment without the bootstrapper:  
 
-```  
+```cmd  
 msbuild /target:publish /property:BootstrapperEnabled=false  
 ```  
 

docs/deployment/choosing-a-clickonce-update-strategy.md

@@ -41,7 +41,7 @@ ms.workload:
 
  This is the same as changing the **Update** element in the deployment manifest as follows:  
 
-```  
+```xml  
 <!-- When to check for updates -->  
 <subscription>  
    <update>  
@@ -59,7 +59,7 @@ ms.workload:
 
  This is the same as changing the **Update** element in the deployment manifest as follows:  
 
-```  
+```xml  
 <!-- When to check for updates -->  
 <subscription>  
    <update>  
@@ -78,7 +78,7 @@ ms.workload:
 
  This is the same as setting the **minimumRequiredVersion** attribute of the **Deployment** element in the deployment manifest; for example:  
 
-```  
+```xml  
 <deployment install="true" minimumRequiredVersion="1.0.0.0">  
 ```