C# Debugging is only supported in official Microsoft-signed binary blob releases of VS Code due to License restrictions and is considered proprietary.
This extension replaces NetCoreDbg
with Samsung's MIT-licensed alternative.
Long-Term Support fork tracks upstream changes built and tested across different platforms. Each release is pegged to provide maximum stability, security, and usability to prevent developer downtime.
Dependency Versions
↗ NetCoreDbg-LTS: Release 1.20.786
↗ OmniSharp-VSCode: Release 1.23.15
Tested Deployments
✔ Code-Server Containers
- Release
3.12.0
- VS Code Release
1.6.0
- Release
1.60.1
- Release
1.60.1
⚠ GitPod
- Debugger fails due to dependency on dotnet runtime env issue #5090
This extension is published at open-vsx.org using Github Actions CI/CD Pipeline.
Requirements:
- nodejs
- npm (comes with nodejs)
git clone https://github.com/muhammadsammy/free-omnisharp-vscode.git
cd free-omnisharp-vscode
npm install
npx gulp 'vsix:release:package'
then run Extensions: Install from VSIX
from the command pallete and select the csharp-VERSION_NUMBER.vsix
file.
Stability Issues and pull requests for improving stability, reported CVE resolutions, or tested improvements are targetted in this repo.
Feature Requests
For issues specific to bugs or features, checkout the upstream repository dependencies netcoredbg
or omnisharp-vscode
.
OmniSharp/omnisharp-vscode README
The .NET 3.1.40x SDKs require version 16.7 of MSBuild.
For MacOS and Linux users who have Mono installed, this means you will need to set omnisharp.useGlobalMono
to never
until a version of Mono ships with MSBuild 16.7.
The .NET 5 SDK requires version 16.8 of MSBuild.
For Windows users who have Visual Studio installed, this means you will need to be on the latest Visual Studio 16.8 Preview.
For MacOS and Linux users who have Mono installed, this means you will need to set omnisharp.useGlobalMono
to never
until a version of Mono ships with MSBuild 16.8.
To enable emmet support, add the following to your settings.json:
"emmet.includeLanguages": {
"aspnetcorerazor": "html"
}
The C# semantic highlighting support is in preview. To enable, set editor.semanticHighlighting.enabled
and csharp.semanticHighlighting.enabled
to true
in your settings. Semantic highlighting is only provided for code files that are part of the active project.
To really see the difference, try the new Visual Studio 2019 Light and Dark themes with semantic colors that closely match Visual Studio 2019.
First install:
- Node.js (8.11.1 or later)
- Npm (5.6.0 or later)
To run and develop do the following:
- Run
npm i
- Run
npm run compile
- Open in Visual Studio Code (
code .
) - Optional: run
npm run watch
, make code changes - Press F5 to debug
To test do the following: npm run test
or F5 in VS Code with the "Launch Tests" debug configuration.
This project is released under MIT, for details refer to LICENSE and upstream RuntimeLicenses