From: Juan Hoyos <19413848+hoyosjs@users.noreply.github.com>
Date: Fri, 12 May 2023 22:02:15 +0000 (-0700)
Subject: Update debugging-runtime.md to mention nativeprereqs (#86174)
X-Git-Tag: accepted/tizen/unified/riscv/20231226.055536~2254
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=87157cd4e1b307f27e67d3bd4cb66296e7f9ea76;p=platform%2Fupstream%2Fdotnet%2Fruntime.git

Update debugging-runtime.md to mention nativeprereqs (#86174)
---

diff --git a/docs/workflow/debugging/coreclr/debugging-runtime.md b/docs/workflow/debugging/coreclr/debugging-runtime.md
index 74a742f..10b63a1 100644
--- a/docs/workflow/debugging/coreclr/debugging-runtime.md
+++ b/docs/workflow/debugging/coreclr/debugging-runtime.md
@@ -41,6 +41,7 @@ If for some reason `System.Private.CoreLib.dll` is missing, you can rebuild it w
 
 Visual Studio's capabilities as a full IDE provide a lot of help making the runtime debugging more amiable.
 
+0. Run `.\build.cmd clr.nativeprereqs -a <architecture> -c <configuration>`. This will build some of the tools requiremented for the native build. This step only needs to be run once as long you don't clean the `artifacts` directory.
 1. Open the CoreCLR solution _(coreclr.sln)_ in Visual Studio.
    * _Method 1_: Use the build scripts to open the solution:
       1. Run `.\build.cmd -vs coreclr.sln -a <architecture> -c <configuration>`. This will create and launch the CoreCLR solution in VS for the specified architecture and configuration. By default, this will be `x64 Debug`.