Skip to content

Commit

Permalink
Add docs link to editing-and-debugging (dotnet#41636)
Browse files Browse the repository at this point in the history
We were missing a link to the Editing and Debugging doc from the main workflow doc.
  • Loading branch information
agocke authored Aug 31, 2020
1 parent 731eaf3 commit 347be9c
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
4 changes: 4 additions & 0 deletions docs/workflow/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,10 @@ On Unix like systems, arguments can be passed in with a single `-` or double hyp
The repository currently consists of different major parts: the runtimes, the libraries, and the installer.
To build just one part you use the root build script (build.cmd/sh), and you add the `-subset` flag.

## Editing and Debugging

For instructions on how to edit code and debug your changes, see [Editing and Debugging](editing-and-debugging.md).

## Configurations

You may need to build the tree in a combination of configurations. This section explains why.
Expand Down
2 changes: 1 addition & 1 deletion docs/workflow/editing-and-debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ what are in the repository. In particular
Thus opening one of these two solution files (double clicking on them in Explorer) is typically all you need
to do most editing.

Notice that the CoreCLR solution is under the 'bin' directory. This is because it is created as part of the build.
Notice that the CoreCLR solution is under the `artifacts` directory. This is because it is created as part of the build.
Thus you can only launch this solution after you have built at least once.

* See [Debugging CoreCLR](debugging/coreclr/debugging.md)
Expand Down

0 comments on commit 347be9c

Please sign in to comment.