Skip to content

Commit f76cda2

Browse files
committed
Move debugger docs and update readme
1 parent 0cc6577 commit f76cda2

20 files changed

+34
-43
lines changed

docs/Installing-without-Internet-connectivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ Some environments may not have access to the Internet and thus the marketplace t
22

33
> NOTE: It is important that if extensions offer platform-specific versions, that you ensure you are downloading/installing the matching platform pieces. Failure to do so could put your VS Code environment in a non-functional state.
44
5-
* Download and install the required .NET 9.0.1 runtime from https://dot.net/downloads
5+
* Download and install the required ASP.NET Core 9.0.8 runtime from https://dot.net/downloads
66
* Download the following VS Code extensions **for your specific platform**:
77
* [.NET Install Tool](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.vscode-dotnet-runtime)
88
* [C# language extension](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp)
99
* Optional extensions such as the [C# Dev Kit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit), [MAUI](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.dotnet-maui), or [IntelliCode for C#](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.vscodeintellicode-csharp)
10-
* Follow the documentation to [**Install from VSIX**](https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix) in VS Code with the downloaded extension files
10+
* Follow the documentation to [**Install from VSIX**](https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix) in VS Code with the downloaded extension files

docs/Reporting-Issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ The extension supports the command that populates the necessary information from
22

33
#### Report issue on GitHub
44
* In VSCode, navigate to the View --> Command Palette menu or press Ctrl+Shift+P.
5-
* Select the option : `CSharp: Start authoring a new issue on GitHub`. This will open the github repository issues page with a new issue with all the necessary system information.
5+
* Select the option : `CSharp: Report an issue`. This will open the github repository issues page with a new issue with all the necessary system information.
66
* Fill in all the fields like "Expected Behavior", "Actual Behavior", "Steps to Reproduce".
7-
* Paste the "OmniSharp log" and the "C#" log (if any) and hit "Submit"
7+
* Paste the "C#" log (if any) and hit "Submit"
88

99
##### OmniSharp and C# log
1010
* In VSCode, navigate to View-->Output or press Ctrl+Shift+U

docs/_Sidebar.md

Lines changed: 0 additions & 36 deletions
This file was deleted.
File renamed without changes.

docs/Attaching-to-remote-processes.md renamed to docs/debugger/Attaching-to-remote-processes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Here is what these options do:
8181

8282
Once this is all setup, then switch to the debug tab in VS Code, open the configuration drop down and select your new configuration ('.NET Core Remote Attach'). You may need to restart VS Code to have your new configuration show up in the list.
8383

84-
![Debug launch configuration](https://raw.githubusercontent.com/wiki/OmniSharp/omnisharp-vscode/images/debug-launch-configurations-remote-attach.png)
84+
![Debug launch configuration](../images/debug-launch-configurations-remote-attach.png)
8585

8686
Once the configuration is selected. Press the play button (F5) to bring up the process selection UI and start debugging.
8787

@@ -195,7 +195,7 @@ If the process failed to attach and there is a similar event to the following:
195195
}
196196
```
197197
198-
and if you are on VsCode, you should see the stderr message:
198+
and if you are on VsCode, you should see the stderr message:
199199
``` vmmap[6174]: [fatal] unable to ask for permission to examine process; run tool using sudo, or without redirecting stdin and stderr. ```
200200
201-
Most likely that Developer Mode is not enabled on your mac machine. You can enable it by typing ```sudo DevToolsSecurity --enable```
201+
Most likely that Developer Mode is not enabled on your mac machine. You can enable it by typing ```sudo DevToolsSecurity --enable```
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)