summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJustin Van Patten <jvp@justinvp.com>2015-07-01 21:13:06 -0700
committerJustin Van Patten <jvp@justinvp.com>2015-07-01 21:13:06 -0700
commit782c9bd39c2717d272e87c1b61ec8b8dd9efb5a2 (patch)
tree4c45a000dbb6a81ea2336e2f1c3bababdbd03f23
parent572b986b2e7ca4bc25e05be96872bcab506b745e (diff)
downloadcoreclr-782c9bd39c2717d272e87c1b61ec8b8dd9efb5a2.tar.gz
coreclr-782c9bd39c2717d272e87c1b61ec8b8dd9efb5a2.tar.bz2
coreclr-782c9bd39c2717d272e87c1b61ec8b8dd9efb5a2.zip
Fix markdown so it renders correctly on GitHub
-rw-r--r--Documentation/building/testing-with-corefx.md22
1 files changed, 12 insertions, 10 deletions
diff --git a/Documentation/building/testing-with-corefx.md b/Documentation/building/testing-with-corefx.md
index 92b94b9d5c..97c81200c5 100644
--- a/Documentation/building/testing-with-corefx.md
+++ b/Documentation/building/testing-with-corefx.md
@@ -6,16 +6,18 @@ It may be valuable to use CoreFX tests to validate your changes to CoreCLR or ms
In order to do this you need to create a file called `localpublish.props` under the `<repo root>\packages` folder.
The contents of the file should look like this (make sure to update the version to the current version of the CoreCLR package used by CoreFx):
- <Project ToolsVersion="12.0" DefaultTargets="Build"
- xmlns="http://schemas.microsoft.com/developer/msbuilding/2003">
- <ItemGroup>
- <LocalPackages Include="$(PackagesBinDir)">
- <PackageName>Microsoft.DotNet.CoreCLR</PackageName>
- <PackageVersion>1.0.2-prerelease</PackageVersion>
- <InstallLocation><corefx repo root>\packages</InstallLocation>
- </LocalPackages>
- </ItemGroup>
- </Project>
+```xml
+<Project ToolsVersion="12.0" DefaultTargets="Build"
+ xmlns="http://schemas.microsoft.com/developer/msbuilding/2003">
+ <ItemGroup>
+ <LocalPackages Include="$(PackagesBinDir)">
+ <PackageName>Microsoft.DotNet.CoreCLR</PackageName>
+ <PackageVersion>1.0.2-prerelease</PackageVersion>
+ <InstallLocation><corefx repo root>\packages</InstallLocation>
+ </LocalPackages>
+ </ItemGroup>
+</Project>
+```
Once this file is there, subsequent builds of the CoreCLR repo will install the CoreCLR package into the location specified by `InstallLocation`.