Update testing with private CoreCLR bits

Remove the `--` to pass in `/p:CoreCLROverridePath` to `build.cmd` as it no longer needed.

Commit migrated from https://github.com/dotnet/corefx/commit/0e7236fda21a07302b14030c82f79bb981c723a6

diff --git a/docs/libraries/project-docs/developer-guide.md b/docs/libraries/project-docs/developer-guide.md
index 0dc461e313d36d0aeec336d0d3c674112d8efbfd..3f33778f88b93dc3e2c9d09b8157a9634afa9649 100644 (file)
--- a/docs/libraries/project-docs/developer-guide.md
+++ b/docs/libraries/project-docs/developer-guide.md
@@ -465,7 +465,7 @@ Generally the CoreFx build system gets the CoreCLR from a NuGet package which ge
 1. Build CoreCLR and note your output directory. Ex: `\coreclr\bin\Product\Windows_NT.x64.Release\` Note this will vary based on your OS/Architecture/Flavor and it is generally a good idea to use Release builds for CoreCLR when running CoreFx tests and the OS and Architecture should match what you are building in CoreFx.
 2. Build CoreFx either passing in the `CoreCLROverridePath` property or setting it as an environment variable:
 ```
-build.cmd -- /p:CoreCLROverridePath=d:\git\coreclr\bin\Product\Windows_NT.x64.Release\
+build.cmd /p:CoreCLROverridePath=d:\git\coreclr\bin\Product\Windows_NT.x64.Release\
 ```
 
 When we copy the files to override the CoreCLR we do a hard-link copy, so in general if you rebuild CoreCLR the new binaries should be reflected in CoreFx for subsequent builds of individual projects in corefx. However if you want to force refresh or if you want to just update the CoreCLR after you already ran `build.cmd` from CoreFx you can run the following command: