diff options
author | Vance Morrison <vancem@microsoft.com> | 2017-07-10 16:23:49 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-07-10 16:23:49 -0700 |
commit | fd4522a2dac7f88a82537af35bdc88c1d856ad47 (patch) | |
tree | 3d46368494ce43c499a2885067c50988f7ed35e6 /Documentation | |
parent | 81b4233b34188c92cf065d0b104089eedbe3907f (diff) | |
download | coreclr-fd4522a2dac7f88a82537af35bdc88c1d856ad47.tar.gz coreclr-fd4522a2dac7f88a82537af35bdc88c1d856ad47.tar.bz2 coreclr-fd4522a2dac7f88a82537af35bdc88c1d856ad47.zip |
Put in a warning that the instructions no longer work properly
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/workflow/UsingYourBuild.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/workflow/UsingYourBuild.md b/Documentation/workflow/UsingYourBuild.md index b83c33efd9..5c25000ff7 100644 --- a/Documentation/workflow/UsingYourBuild.md +++ b/Documentation/workflow/UsingYourBuild.md @@ -117,6 +117,8 @@ could update these locations in place, but that is not recommended since they ar ## Update CoreCLR using runtime nuget package +# WARNING: TODO: This section has been broken when Microsoft.Netcore.App included the CorCLR binaries. We need to update this. + Updating CoreCLR from raw binary output is easier for quick one-off testing but using the nuget package is better for referencing your CoreCLR build in your actual application because of it does not require manual copying of files around each time the application is built and plugs into the rest of the tool chain. This set of instructions will cover |