Update links to use dotnet/vscode-csharp

Author: JoeRobich

docs/C#-Extension-support-for-new-Linux-Distros-with-.NET-Core.md

@@ -6,10 +6,10 @@ There are four buckets that various Linux distros might fall into --
 In this case the C# extension team should be able to produce a new version of the C# extension fairly soon after the .NET Core team publishes nuget packages which the C# extension can download.
 
 ### 2: .NET Core and vsdbg from another distro are binary compatible
-In this case it is just a matter of tweaking this [switch statement](https://github.com/OmniSharp/omnisharp-vscode/blob/a0d803fb0e30832b3a8c034e938c2e97662f9788/src/platform.ts#L226) which parses the output from `cat /etc/os-release`. While we cannot commit to testing on these unofficial distros we are happy to accept a PR to enable the distro, and if there are minor bugs in the debugger we are happy to try and fix them as well.
+In this case it is just a matter of tweaking this [switch statement](https://github.com/dotnet/vscode-csharp/blob/a0d803fb0e30832b3a8c034e938c2e97662f9788/src/platform.ts#L226) which parses the output from `cat /etc/os-release`. While we cannot commit to testing on these unofficial distros we are happy to accept a PR to enable the distro, and if there are minor bugs in the debugger we are happy to try and fix them as well.
 
 ### 3: The community has produced a .NET Core install script, and the public vsdbg can run
-For these distributions, the [debugger installer class](https://github.com/OmniSharp/omnisharp-vscode/blob/master/src/coreclr-debug/install.ts) can be run as a [gulp task](https://github.com/OmniSharp/omnisharp-vscode/blob/bc2eb6e5ec90f3b2c9e5a45e3aadd47e28539d01/gulpfile.js#L64). So it might be possible for the community to provide an install script which will find the current installed C# extension, use gulp to have the debugger and OmniSharp download the version of the extension from some other Linux distro, and then patch the CoreCLR/FX which they are running on. The C# extension team is happy to accept tweaks to the install code to make this easier.
+For these distributions, the [debugger installer class](https://github.com/dotnet/vscode-csharp/blob/master/src/coreclr-debug/install.ts) can be run as a [gulp task](https://github.com/dotnet/vscode-csharp/blob/bc2eb6e5ec90f3b2c9e5a45e3aadd47e28539d01/gulpfile.js#L64). So it might be possible for the community to provide an install script which will find the current installed C# extension, use gulp to have the debugger and OmniSharp download the version of the extension from some other Linux distro, and then patch the CoreCLR/FX which they are running on. The C# extension team is happy to accept tweaks to the install code to make this easier.
 
 ### 4: New vsdbg is needed
-vsdbg is the cross-platform .NET Core debugger backend. It is based on the same debugger as Visual Studio, and so is a closed-sound product. Distributions where the current public version of vsdbg cannot run are difficult to deal with. In general, we would need official support from the .NET Core team in these cases. Though feel free to open an [issue](https://github.com/OmniSharp/omnisharp-vscode/issues) to discuss the problem.
+vsdbg is the cross-platform .NET Core debugger backend. It is based on the same debugger as Visual Studio, and so is a closed-sound product. Distributions where the current public version of vsdbg cannot run are difficult to deal with. In general, we would need official support from the .NET Core team in these cases. Though feel free to open an [issue](https://github.com/dotnet/vscode-csharp/issues) to discuss the problem.

docs/How-to-run-and-debug-unit-tests.md

@@ -5,9 +5,9 @@ The C# extension currently supports running and debugging a unit test via CodeLe
 ### Notes
 
 * Because `dotnet test` will run the test code in a child process, it isn't possible to configure a "unit test debugging" configuration in launch.json
-* There currently isn't a VS Code command to run the current test, though there is an [issue for this in the backlog](https://github.com/OmniSharp/omnisharp-vscode/issues/421).
-* You can tweak [debugging options](https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md) for unit tests by opening your VS Code settings file (ex: File->Preferences->Settings on Windows), and configuring the `"csharp.unitTestDebuggingOptions"` setting. See example below.
-* If your unit tests are targeting .NET Framework instead of .NET Core, see [Desktop .NET Framework](https://github.com/OmniSharp/omnisharp-vscode/wiki/Desktop-.NET-Framework) for more information.
+* There currently isn't a VS Code command to run the current test, though there is an [issue for this in the backlog](https://github.com/dotnet/vscode-csharp/issues/421).
+* You can tweak [debugging options](https://github.com/dotnet/vscode-csharp/blob/master/debugger-launchjson.md) for unit tests by opening your VS Code settings file (ex: File->Preferences->Settings on Windows), and configuring the `"csharp.unitTestDebuggingOptions"` setting. See example below.
+* If your unit tests are targeting .NET Framework instead of .NET Core, see [Desktop .NET Framework](https://github.com/dotnet/vscode-csharp/wiki/Desktop-.NET-Framework) for more information.
 
 Example User Settings file with unit test debugging options:
 

docs/Troubleshooting:-'The-.NET-Core-SDK-cannot-be-located.'-errors.md

@@ -70,7 +70,7 @@ Note that, as of the time of this writing, there are also other incompatibilitie
 
 More information about this problem can be found in [dotnet/cli#12110](https://github.com/dotnet/cli/issues/12110).
 
-Some community members have been successful in using the Snap install by following the instructions listed in [Configuring Snap installs of dotnet-sdk](https://github.com/OmniSharp/omnisharp-vscode/wiki/Configuring-Snap-installs-of-dotnet-sdk).
+Some community members have been successful in using the Snap install by following the instructions listed in [Configuring Snap installs of dotnet-sdk](https://github.com/dotnet/vscode-csharp/wiki/Configuring-Snap-installs-of-dotnet-sdk).
 
 Another possible workaround is to add the following to `~/.omnisharp/omnisharp.json`.
 
@@ -84,4 +84,4 @@ Another possible workaround is to add the following to `~/.omnisharp/omnisharp.j
 
 Instead, you also may create a symbolic link to your dotnet install like so:
 
-`ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet`
+`ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet`

docs/debugger/.NET-Core-debugging-feature-list.md

@@ -2,11 +2,11 @@ The following table describes the feature list for .NET Core debugging using VS
 
 | Feature   | Description | Visual Studio Code | Visual Studio For Mac | Visual Studio |  Availability |
 | --------- | ----------- | :----------------: | :-------------------: | :-----------: | ------------- |
-| Breakpoints | Adding / removing breakpoints | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview | 
+| Breakpoints | Adding / removing breakpoints | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview |
 | Execution control | Step through code (including async stepping), pause, continue | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|
-| Launch / Attach | Includes launching, attaching to, detaching from and terminating the target app | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|  
-| EE | This is the ability to view variables, custom expressions in locals / watch windows | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|  
-| Just my code | This is the ability to hide external code during debugging | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|  
+| Launch / Attach | Includes launching, attaching to, detaching from and terminating the target app | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|
+| EE | This is the ability to view variables, custom expressions in locals / watch windows | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|
+| Just my code | This is the ability to hide external code during debugging | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.2.2 / VS For Mac Preview|
 | Conditional breakpoints | This is the ability to stop on a breakpoint when the given condition is satisfied | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.3.0 / VS For Mac Preview|
 | Debugging Razor views | This is the ability to debug embedded code in cshtml files | :white_check_mark: | :white_check_mark: | N/A | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.3.0 |
 | Edit variable values | This is the ability to update the value of a variable inside locals / watch windows | :white_check_mark: | :white_check_mark: | :white_check_mark: | VS2015.3 + [MIEngine](https://github.com/Microsoft/MIEngine/wiki/Building-the-MIEngine) / C# ext 1.3.0 / VS For Mac Preview|
@@ -16,10 +16,10 @@ The following table describes the feature list for .NET Core debugging using VS
 | Symbol Server | This is the ability to specify a remote server to pull down pdbs for code being debugged | [Work Item](https://github.com/dotnet/roslyn/issues/6881) | [Work Item](https://github.com/dotnet/roslyn/issues/6881) | [Work Item](https://github.com/dotnet/roslyn/issues/6881) |
 | Source Server | This is the ability to pull down sources from a remote server for code being debugged | [Work Item](https://github.com/dotnet/roslyn/issues/5397) [Work Item](https://github.com/dotnet/roslyn/issues/4119)| [Work Item](https://github.com/dotnet/roslyn/issues/5397) [Work Item](https://github.com/dotnet/roslyn/issues/4119) | [Work Item](https://github.com/dotnet/roslyn/issues/5397) [Work Item](https://github.com/dotnet/roslyn/issues/4119) | |
 | Manual symbol loading | This is the ability to locate and load symbols for a module anytime during a debug session | | | | |
-| Function bps | This is the ability to stop the debugger at the start of a given function | [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/295)| [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/295) | [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/295) |
-| Hit count bps | This is the ability to stop the debugger after a breakpoint is hit given number of times | [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/895)| [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/895) | [Work Item](https://github.com/OmniSharp/omnisharp-vscode/issues/895) |
+| Function bps | This is the ability to stop the debugger at the start of a given function | [Work Item](https://github.com/dotnet/vscode-csharp/issues/295)| [Work Item](https://github.com/dotnet/vscode-csharp/issues/295) | [Work Item](https://github.com/dotnet/vscode-csharp/issues/295) |
+| Hit count bps | This is the ability to stop the debugger after a breakpoint is hit given number of times | [Work Item](https://github.com/dotnet/vscode-csharp/issues/895)| [Work Item](https://github.com/dotnet/vscode-csharp/issues/895) | [Work Item](https://github.com/dotnet/vscode-csharp/issues/895) |
 | Edit and Continue | This is the ability to make code changes during a debugging session without having to restart a new session | [Work Item](https://github.com/dotnet/roslyn/issues/1952) | [Work Item](https://github.com/dotnet/roslyn/issues/1952) | [Work Item](https://github.com/dotnet/roslyn/issues/1952) |
 | Dump debugging | This is the ability to debug crash dumps | | | | |
 | Return values | This is the ability to see the values a function returns as the user is stepping through the code | | | | |
 | Visualizers | This is the ability to invoke a custom UI for visualizing a value in the locals / watch windows | | | | |
-| Step Into Specific | This is the ability to select a particular function to step into when the current instruction pointer is on a line that contains multiple functions to be called | | | | 
+| Step Into Specific | This is the ability to select a particular function to step into when the current instruction pointer is on a line that contains multiple functions to be called | | | |

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

@@ -91,7 +91,7 @@ Last, to be able to debug obviously the application must somehow be runnable on
 
 There are two special concerns in this area when it comes to debugging:
 
-1. Debug vs. Release Configuration: If you are going to be debugging, the experience is going to be much better if the debug configuration of your application is running instead of the release configuration. If this isn't possible, one can debug release code. To do this, disable [justMyCode](https://github.com/OmniSharp/omnisharp-vscode/blob/release/debugger.md#just-my-code) in launch.json.
+1. Debug vs. Release Configuration: If you are going to be debugging, the experience is going to be much better if the debug configuration of your application is running instead of the release configuration. If this isn't possible, one can debug release code. To do this, disable [justMyCode](https://github.com/dotnet/vscode-csharp/blob/release/debugger.md#just-my-code) in launch.json.
 2. PDB files: In order for VSDBG to be able to be able to map executable code back to its source code (or vice versa) VSDBG needs to have PDB files. If you are already building your application on the target server, this is taken care of for you. If you are building it somewhere else, you need to make sure to copy the PDB files next to their associated dll or set the DebugType to 'embedded' so that the PDB data is kept inside of the compiled dll.
 
 ### Configuring Docker attach with launch.json
@@ -156,7 +156,7 @@ If vsdbg is crashing or being aborted a few additional troubleshooting steps:
 
 #### 1: Check for libicu compatibility
 
-See the [Testing libicu compatibility on Linux](https://github.com/OmniSharp/omnisharp-vscode/wiki/Testing-libicu-compatibility-on-Linux) page for more information.
+See the [Testing libicu compatibility on Linux](https://github.com/dotnet/vscode-csharp/wiki/Testing-libicu-compatibility-on-Linux) page for more information.
 
 #### 2: Save a coredump of a possible vsdbg crash
 

docs/debugger/Desktop-.NET-Framework.md

@@ -1,12 +1,12 @@
-The C# extension supports limited full .NET framework debugging. It can only debug 64-bit applications with [portable PDBs](https://github.com/OmniSharp/omnisharp-vscode/wiki/Portable-PDBs).
+The C# extension supports limited full .NET framework debugging. It can only debug 64-bit applications with [portable PDBs](https://github.com/dotnet/vscode-csharp/wiki/Portable-PDBs).
 
 To enable the Desktop CLR debugger, change the configuration type in launch.json to be "clr" instead of "coreclr" and program should be pointing at the exe (**NOT** a .dll).
 
 For unit tests, this can be done thusly:
 1. File->Preferences->Settings
 2. Open "CSharp: Unit Test Debugging Options"
 3. Set the 'type' to 'clr' (see settings.json example below)
-4. NOTE: For MSTest projects, also see [Forcing MSTest projects to use a 64-bit worker](https://github.com/OmniSharp/omnisharp-vscode/wiki/Desktop-.NET-Framework#forcing-mstest-projects-to-use-a-64-bit-worker) section.
+4. NOTE: For MSTest projects, also see [Forcing MSTest projects to use a 64-bit worker](https://github.com/dotnet/vscode-csharp/wiki/Desktop-.NET-Framework#forcing-mstest-projects-to-use-a-64-bit-worker) section.
 
 ## launch.json example
 
@@ -49,4 +49,4 @@ To fix this:
     <TargetPlatform>x64</TargetPlatform>
   </RunConfiguration>
 </RunSettings>
-```
+```

docs/debugger/Diagnosting-'Debug-adapter-process-has-terminated-unexpectedly'.md

@@ -1,7 +1,7 @@
 If Visual Studio code displays "Debug adapter process has terminated unexpectedly", and the debug console doesn't have information about why, this generally means that the debugger process (vsdbg-ui) crashed. Here is some information you can provide us to diagnose what went wrong.
 
 ### Common
-On all OSs, it can be useful to have [logging enabled](https://github.com/OmniSharp/omnisharp-vscode/wiki/Enabling-C%23-debugger-logging), and to provide the last bit of the event log.
+On all OSs, it can be useful to have [logging enabled](https://github.com/dotnet/vscode-csharp/wiki/Enabling-C%23-debugger-logging), and to provide the last bit of the event log.
 
 ### macOS
 
@@ -66,8 +66,8 @@ Faulting application start time: 0x01d2cf58f1e7031e
 Faulting application path: C:\Users\greggm\.vscode\extensions\ms-dotnettools.csharp-1.21.18\.debugger\vsdbg-ui.exe
 Faulting module path: C:\Users\greggm\.vscode\extensions\ms-dotnettools.csharp-1.21.18\.debugger\vsdbg.DLL
 Report Id: 694807aa-44e0-42d3-8129-437f457a5efd
-Faulting package full name: 
-Faulting package-relative application ID: 
+Faulting package full name:
+Faulting package-relative application ID:
 ```
 
 ### Linux

docs/debugger/Microsoft-.NET-Core-Debugger-licensing-and-Microsoft-Visual-Studio-Code.md

@@ -10,4 +10,4 @@ The C# extension for Visual Studio Code includes the Microsoft .NET Core Debugge
 
 If you installed the OSS version of VS Code, you can uninstall it and reinstall the Microsoft version from [https://code.visualstudio.com/download](https://code.visualstudio.com/download).
 
-If you believe you have the Microsoft version installed and you are still seeing this problem, you can [open an issue](https://github.com/omnisharp/omnisharp-vscode/issues) in this repo.
+If you believe you have the Microsoft version installed and you are still seeing this problem, you can [open an issue](https://github.com/dotnet/vscode-csharp/issues) in this repo.