Merge pull request NuGet#157 from NuGet/kraigb

Mark code languages for issue 146

Author: Kraig Brockschmidt

docs/API/NuGet-Credential-Providers-for-Visual-Studio.md

@@ -65,6 +65,7 @@ During credential acquisition, the credential service will try credential provid
 
 To create a NuGet credential provider for Visual Studio, create a Visual Studio Extension that exposes a public MEF Export implementing the `IVsCredentialProvider` type, and adheres to the principles outlined below.
 
+    ```cs
     public interface IVsCredentialProvider
     {
         Task<ICredentials> GetCredentialsAsync(
@@ -75,6 +76,7 @@ To create a NuGet credential provider for Visual Studio, create a Visual Studio
           bool nonInteractive,
           CancellationToken cancellationToken);
     }
+    ```
 
 A sample implementation can be found in [the VsCredentialProvider sample](https://github.com/NuGet/Samples/tree/master/VsCredentialProvider).
 

docs/Consume-Packages/Configuring-NuGet-Behavior.md

@@ -79,9 +79,11 @@ To **remove a value**, use the same commands but with an empty value, such as:
 
 To create a new configuration file, copy the template below into that file and then use the `nuget config --configFile <filename>` command to set values:
 
+    ```xml
     <?xml version="1.0" encoding="utf-8"?>
     <configuration>
     </configuration>
+    ```
 
 > [!Warning]
 > Although you can modify the file in any text editor, NuGet (v3.4.3 and later) silently ignores the entire configuration file if it contains malformed XML (mismatched tags, invalid quotation marks, etc.).
@@ -153,15 +155,18 @@ You then have four `NuGet.Config` files in the following locations with the give
 
 1. Global configuration file, `%APPDATA%\NuGet\Nuget.config`:
 
+        ```xml
         <?xml version="1.0" encoding="utf-8"?>
         <configuration>
           <activePackageSource>
             <add key="NuGet official package source" value="https://nuget.org/api/v2/" />
           </activePackageSource>
         </configuration>
+        ```
 
 1. `d:\NuGet.config`:
 
+        ```xml
         <?xml version="1.0" encoding="utf-8"?>
         <configuration>
         <config>
@@ -171,9 +176,11 @@ You then have four `NuGet.Config` files in the following locations with the give
             <add key="enabled" value="True" />
           </packageRestore>
         </configuration>
+        ```
 
 1. `d:\Project1\NuGet.config`:
 
+        ```xml
         <?xml version="1.0" encoding="utf-8"?>
         <configuration>
           <config>
@@ -185,16 +192,19 @@ You then have four `NuGet.Config` files in the following locations with the give
             <add key="MyPrivateRepo - ES" value="https://MyPrivateRepo/ES/nuget" />
           </packageSources>
         </configuration>
+        ```
 
 1. `d:\Project2\NuGet.config`:
 
+        ```xml
         <?xml version="1.0" encoding="utf-8"?>
         <configuration>
           <packageSources>
           <!-- Add this repository to the list of available repositories -->
             <add key="MyPrivateRepo - DQ" value="https://MyPrivateRepo/DQ/nuget" />
           </packageSources>
         </configuration>
+        ```
 
 Here's how NuGet will load and apply the settings, depending on where it's invoked:
 
@@ -227,6 +237,7 @@ The defaults file works with the following settings:
 
 The following is an example NuGetDefaults.config file containing each of its allowable sections:
 
+    ```xml
     <?xml version="1.0" encoding="UTF-8"?>
     <configuration>
         <!-- DefaultPushSource key is similar to the 'DefaultPushSource' key of NuGet.config schema-->
@@ -251,3 +262,4 @@ The following is an example NuGetDefaults.config file containing each of its all
             <add key="nuget.org" value="true" />
         </disabledPackageSources>
     </configuration>
+    ```

docs/Consume-Packages/Dependency-Resolution.md

@@ -79,9 +79,10 @@ The lock file is temporary and does not need to be added to source control; it's
 
 NuGet 3.x applies four main rules to resolve dependencies: lowest applicable version, floating versions, nearest-wins, cousin dependencies.
 
-#### Lowest applicable version
 <a name="lowest-applicable-version"></a>
 
+#### Lowest applicable version
+
 NuGet 3.x restores the lowest possible version of a package as defined by its dependencies. This rule also applied to dependencies on the application or the class library unless declared as [floating](#floating-versions).
 
 For example, in the following figure *1.0-Beta* is considered lower than *1.0* so NuGet chooses the 1.0 version:
@@ -96,18 +97,19 @@ When an application specifies an exact version number, such as *1.2*, that is no
 
 ![NuGet generates an error when an exact package version is not available](media/projectJson-dependency-3.png)
 
-#### Floating versions
 <a name="floating-versions"></a>
 
+#### Floating versions
+
 A floating dependency version is specified with the * wildcard, as with *6.0.\** in the `project.json` file. This says "use the latest 6.0.x version"; a floating version of *4.\** means "use the latest 4.x version." Using a floating version allows a dependency package to continue evolving without requiring a change to the consuming application (or package).
 
 When a floating version constraint is specified then NuGet will resolve the highest version of a package that matches the version pattern, for example *6.0.** will get the highest version of a package that starts with *6.0*:
 
 ![Choosing version 6.0.1 when a floating version 6.0.* is requested](media/projectJson-dependency-4.png)
 
+<a name="nearest-wins"></a>
 
 #### Nearest wins
-<a name="nearest-wins"></a>
 
 When the package graph for an application contains different versions of the same package, the package that's closest to the application in the graph will be used and others will be ignored. This allows an application to override any particular package version in the dependency graph.
 
@@ -122,9 +124,10 @@ This rule also results in greater efficiency with large dependency graph (such a
 
 ![When NuGet ignores a package in the graph, it ignores that entire branch](media/projectJson-dependency-6.png)
 
-#### Cousin dependencies
 <a name="cousin-dependencies"></a>
 
+#### Cousin dependencies
+
 When different package versions are referred to at the same distance in the graph from the application, NuGet uses the lowest version that satisfies all version requirements (as with the [lowest applicable version](#lowest-applicable-version) and [floating versions](#floating-versions) rules). In the image below, for example, version *2.0* of Package B will satisfy the other *>=1.0* constraint, and will thus be used:
 
 ![Resolving cousin dependencies using the lower version that satisfies all constraints](media/projectJson-dependency-7.png)

docs/Consume-Packages/Finding-and-Choosing-Packages.md

@@ -52,9 +52,9 @@ You can also search using the package ID, if you know it. See [Search Syntax](#s
 
 At this time, search results are sorted only by relevance, so you generally want to look through at least the first few pages of results for packages that suit your needs, or refine your search terms to be more specific.
 
+<a name="native-c++-packages"></a>
 
 ### Native C++ packages
-<a name="native-c++-packages"></a>
 
 NuGet 2.5+ supports native C++ packages can that can be used in C++ projects in Visual Studio. This enables the **Manage NuGet Packages** context-menu command for projects, introduces a `native` target framework, and provides MSBuild integration.
 

docs/Consume-Packages/Package-References-in-Project-Files.md

@@ -38,40 +38,47 @@ Package references, using the `PackageReference` node, allow you to manage NuGet
 
 You can add a dependency in your project file using the following syntax:
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
         <PackageReference Include="Contoso.Utility.UsefulStuff">
             <Version>3.6.0</Version>
         </PackageReference>
         <!-- ... -->
     </ItemGroup>
+    ```
 
 or, alternately:
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
         <PackageReference Include="Contoso.Utility.UsefulStuff" Version="3.6.0" />
         <!-- ... -->
     </ItemGroup>
+    ```
 
 ## Controlling dependency version
 
 The convention for specifying version remains unchanged:
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
         <PackageReference Include="Contoso.Utility.UsefulStuff">
             <Version>3.6.0</Version>
         </PackageReference>
         <!-- ... -->
     </ItemGroup>
+    ```
 
 In the example above, 3.6.0 means any version that is >=3.6.0 with preference for the lowest version, as described on [version ranges](../create-packages/dependency-versions.md#version-ranges).
 
 ## Floating Versions
 
 [Floating versions](../consume-packages/dependency-resolution.md#floating-versions) are supported with `PackageReference`:
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
         <PackageReference Include="Contoso.Utility.UsefulStuff">
@@ -83,11 +90,13 @@ In the example above, 3.6.0 means any version that is >=3.6.0 with preference fo
         </PackageReference>
         <!-- ... -->
     </ItemGroup>
+    ```
 
 ## Controlling dependency assets
 
 You might be using a dependency purely as a development harness and might not want to expose that to projects that will consume your package. In this scenario, you can use the `PrivateAssets` metadata to control this behavior.
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
 
@@ -97,6 +106,7 @@ You might be using a dependency purely as a development harness and might not wa
 
         <!-- ... -->
     </ItemGroup>
+    ```
 
 The following metadata tags control dependency assets:
 
@@ -120,6 +130,7 @@ Allowable values for these tags are as follows, with multiple values separated b
 
 In the following example, everything except the content files from the package would be consumed by the project and everything except content files and analyzers would flow to the parent project.
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
 
@@ -131,6 +142,7 @@ In the following example, everything except the content files from the package w
 
         <!-- ... -->
     </ItemGroup>
+    ```
 
 Note that because `build` is not included with `PrivateAsset`, targets and props *will* flow to the parent project. Consider, for example, that the reference above is used in a project that builds a NuGet package called AppLogger. AppLogger can consume the targets and props from Contoso.Utility.UsefulStuff, as can projects that consume AppLogger.
 
@@ -140,20 +152,23 @@ You can use a condition to control whether a package is included, where conditio
 
 For example, say you're targeting `netstandard1.4` as well as `net452` but have a dependency that is applicable only for `net452`. In this case you don't want a `nestandard1.4` project that's consuming your package to add that unnecessary dependency. To prevent this, you specify a condition on the `PackageReference` as follows:
 
+    ```xml
     <ItemGroup>
         <!-- ... -->
         <PackageReference Include="Newtonsoft.json" Condition="'$(TargetFramework)' == 'net452'">
             <Version>9.0.1</Version>
         </PackageReference>
         <!-- ... -->
     </ItemGroup>
+    ```
 
 A package built using this project will show that Newtonsoft.json is included as a dependency only for a `net452` target:
 
 ![The result of applying a Condition on PackageReference](media/PackageReference-Condition.png)
 
 Conditions can also be applied at the `ItemGroup` level and will apply to all children `PackageReference` elements:
 
+    ```xml
     <ItemGroup Condition = "'$(TargetFramework)' == 'net452'>
         <!-- ... -->
 
@@ -165,3 +180,4 @@ Conditions can also be applied at the `ItemGroup` level and will apply to all ch
 
         <!-- ... -->
     </ItemGroup>
+    ```

docs/Consume-Packages/Package-Restore.md

@@ -60,13 +60,15 @@ Package restore is primarily enabled through **Tools > Options > [NuGet] Package
 
 - **Allow NuGet to download missing packages** enables all forms of package restore by changing the `packageRestore/enabled` setting in the `%AppData%\NuGet\NuGet.config` file as shown below. (For NuGet 2.6 or earlier, this setting can also be used in a project-specific `.nuget\nuget.config` file.)
 
+        ```xml
         ...
         <configuration>
           <packageRestore>
               <!-- Disables command-line, automatic, and MSBuild-Integrated restore -->
             <add key="enabled" value="False" />
           </packageRestore>
         </configuration>
+        ```
 
 
 > [!Note]
@@ -75,13 +77,15 @@ Package restore is primarily enabled through **Tools > Options > [NuGet] Package
 
 - **Automatically check for missing packages during build in Visual Studio** enables automatic restore for NuGet 2.7 and later by changing the `packageRestore/automatic` setting in the `%AppData%\NuGet\NuGet.config` file as shown below.
 
+        ```xml
         ...
         <configuration>
           <packageRestore>
             <!-- Disables automatic restore in Visual Studio -->
             <add key="automatic" value="False" />
           </packageRestore>
         </configuration>
+        ```
 
 For reference, see the [NuGet config file - packageRestore section](../schema/nuget.config-file.md#packagerestore-section).
 
@@ -95,11 +99,15 @@ When NuGet restores packages through any method, it will honor any constraints s
 
 - `packages.config`: Specify a version range in the `allowedVersion` property of the dependency. See [Reinstalling and Updating Packages](../consume-packages/reinstalling-and-updating-packages.md#constraining-upgrade-versions). For example:
 
+        ```xml
         <package id="Newtonsoft.json" version="6.0.4" allowedVersions="[6,7)" />
+        ```
 
 - `project.json`: Specify a version range directly with the dependency's version number. For example:
 
+        ```json
         "newtonsoft.json": "[6, 7)"
+        ```
 
 In both cases, use the notation described in [Dependency versions](../create-packages/dependency-versions.md).
 
@@ -185,6 +193,7 @@ The process is as follows:
     a. Remove the `.nuget` folder from the solution and the solution workspace.
 1. Edit each project file in the solution, remove the `&lt;RestorePackages&gt;` element, and remove any references to the `nuget.targets` file. Those settings generally appear as follows:
 
+        ```xml
         <RestorePackages>true</RestorePackages>
         ...
         <Import Project="$(SolutionDir)\.nuget\nuget.targets" />
@@ -195,6 +204,7 @@ The process is as follows:
             </PropertyGroup>
             <Error Condition="!Exists('$(SolutionDir)\.nuget\NuGet.targets')" Text="$([System.String]::Format('$(ErrorText)', '$(SolutionDir)\.nuget\NuGet.targets'))" />
         </Target>
+        ```
 
 > [!Tip]    
 > Owen Johnson has created a [PowerShell migration script](https://github.com/owen2/AutomaticPackageRestoreMigrationScript) that can work in many cases, but is used at your own risk. Be sure to commit your project to source control or make a backup before using it.</div>

docs/Consume-Packages/Packages-and-Source-Control.md

@@ -75,12 +75,14 @@ To disable source control integration with TFVC for selected files:
 1. In that folder, create a file named `NuGet.config` and open it for editing.
 1. Add the following text as a minimum, where the [disableSourceControlIntegration](../schema/nuget.config-file.md#solution-section) setting instructs Visual Studio to skip everything in the `packages` folder:
 
+        ```xml
         <?xml version="1.0" encoding="utf-8"?>
         <configuration>
             <solution>
                 <add key="disableSourceControlIntegration" value="true" />
             </solution>
         </configuration>
+        ```
 
 1. If you are using TFS 2010 or earlier, cloak the `packages` folder in your workspace mappings.
 1. On TFS 2012 or later, or with Visual Studio Team Services, add a [`.tfignore`](https://msdn.microsoft.com/en-us/library/ms245454.aspx#tfignore) file with the content below to explicitly ignore modifications to the `\packages` folder on the repository level and a few other intermediate files. (You can create the file in Windows Explorer using the name a `.tfignore.` with the trailing dot, but you might need to disable the "Hide known file extensions" option first.):

docs/Consume-Packages/Reinstalling-and-Updating-Packages.md

@@ -83,11 +83,13 @@ In projects using `packages.config`, the same behavior applies unless you specif
 
 To set a constraint, open `packages.config` in a text editor, locate the dependency in question, and add the `allowedVersions` attribute with a version range. For example, to constrain updates to version 1.x, set `allowedVersions` to `[1,2)`:
 
+    ```xml
     <?xml version="1.0" encoding="utf-8"?>
     <packages>
         <package id="ExamplePackage" version="1.1.0" allowedVersions="[1,2)" />
 
         <!-- ... -->
     </packages>
+    ```
 
 In all cases, use the notation described in [Dependency versions](../create-packages/dependency-versions.md).

docs/Consume-Packages/Team-Foundation-Build.md

@@ -99,11 +99,13 @@ The source code is under the `src` folder. Although our demo only uses a single
 > [!Note]
 > There is currently a [known bug in the NuGet client](https://nuget.codeplex.com/workitem/4072) that causes the client to still add the `packages` folder to version control. A workaround is to disable the source control integration. In order to do that, you'll need a `nuget.config ` file in the  `.nuget` folder that is parallel to your solution. If this folder doesn't exist yet, you'll need to create it. In [`nuget.config`](../consume-packages/configuring-nuget-behavior.md), add the following content:
 
+    ```xml
     <configuration>
         <solution>
             <add key="disableSourceControlIntegration" value="true" />
         </solution>
     </configuration>
+    ```
 
 
 In order to communicate to the version control that we don’t intent to check-in the **packages** folders, we've also added ignore files for both git (`.gitignore`) as well as TF version control (`.tfignore`). These files describes patterns of files you don't want to check-in.
@@ -144,6 +146,7 @@ This project will have the three conventional targets `Clean`, `Build` and `Rebu
 
 The result looks as follows:
 
+    ```xml
     <?xml version="1.0" encoding="utf-8"?>
     <Project ToolsVersion="4.0"
              DefaultTargets="Build"
@@ -181,6 +184,7 @@ The result looks as follows:
                  Projects="@(Solution)" />
       </Target>
     </Project>
+    ```
 
 ## Configuring Team Build