Welcome to the C# extension for Visual Studio Code! This extension provides the following features inside VS Code:
- Lightweight development tools for .NET Core.
- Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc.
- Debugging support for .NET Core (CoreCLR). NOTE: Mono debugging is not supported. Desktop CLR debugging has limited support.
- Support for project.json and csproj projects on Windows, macOS and Linux.
The C# extension is powered by OmniSharp.
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.
-
Greatly improved download experience: when the C# extension is downloaded from the VS Code Marketplace, it will include all of its dependencies already (#4775)
-
Fix typo in Readme.md (PR: #4819)
-
Fix indentation level and spacing for xUnit fact snippet. (PR: #4831)
-
Support relative paths with omnisharp.testRunSettings (PR: #4860) (PR: #4849)
-
Add
CimAttachItemsProvider
to replaceWmicAttachItemsProvider
(PR: #4848) -
Enhance sourceFileMap documentation (PR: #4844)
-
Update the indentation level and spacing for the '"xUnit Test" fact' snippet. (PR: #4831)
-
Debugger changes:
-
Update OmniSharp version to 1.37.17:
- Update versions to match dotnet SDK 6.0.1xx (PR: omnisharp-roslyn#2262)
- Remove all completion commit characters in suggestion mode. (omnisharp-roslyn#1974, omnisharp-roslyn#3219, omnisharp-roslyn#3647, omnisharp-roslyn#4833, PR: omnisharp-roslyn#2253)
- fixed logging interpolation in ProjectManager (PR: omnisharp-roslyn#2246)
- Support signature help for implicit object creation (omnisharp-roslyn#2243, PR: omnisharp-roslyn#2244)
- Implement /v2/gotodefinition for Cake (omnisharp-roslyn#2209, PR: omnisharp-roslyn#2212)
- Show decompilation authorization once per install. (#3982, PR: #4760)
- Launch with first Folder or Solution target found (PR: #4780)
- Update Debugger Labels (PR: #4798)
- Add Debug Welcome View (PR: #4797)
- Update OmniSharp version to 1.37.16:
- Update included Build Tools to match .NET SDK 6 (PR: omnisharp-roslyn#2239)
- Add Custom .NET CLI support to OmniSharp (PR: omnisharp-roslyn#2227)
- Handle .editorconfig changes without running a new design time build (omnisharp-roslyn#2112 PR: omnisharp-roslyn#2234)
- Do not return nulls when getting documents by path (omnisharp-roslyn#2125 PR: omnisharp-roslyn#2233)
- handle RecordStructName in semantic highlighting classification (omnisharp-roslyn#2228 PR: omnisharp-roslyn#2232)
- Update CodeStructureService with FileScoped Namespace support (omnisharp-roslyn#2225 PR: omnisharp-roslyn#2226)
-
Restore launch target for workspace root when no solution present (#4691, PR: #4695)
-
Don't create launch.json for no select process (omnisharp-roslyn#4696, PR: #4699)
-
Support inserting outside code when texts are selected (PR: #4715)
-
Update OmniSharp version to 1.37.15:
- Update Roslyn to 4.0.0-4.21427.11 (PR: omnisharp-roslyn#2220)
- Update NuGet to 5.10.0 (omnisharp-roslyn#2027, PR: omnisharp-roslyn#2034)
- Remove .NET Core 2.1 (PR: omnisharp-roslyn#2219)
- Update versions to match .NET SDK 6 RC1 (PR: omnisharp-roslyn#2217)
- Use FullPaths for Locations that are returned with relative paths. (omnisharp-roslyn#2215, PR: omnisharp-roslyn#2216)
- Improved logging in project manager (PR: omnisharp-roslyn#2203)
- Log a warning when external features path has no assemblies (omnisharp-roslyn#2201, PR: omnisharp-roslyn#2202)
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.
Currently, the C# debugger officially supports the following operating systems:
- X64 operating systems:
- Windows 7 SP1 and newer
- macOS 10.12 (Sierra) and newer
- Linux: see .NET Core documentation for the list of supported distributions. Note that other Linux distributions will likely work as well as long as they include glibc and OpenSSL.
- ARM operating systems:
- Linux is supported as a remote debugging target
To file a new issue to include all the related config information directly from vscode by entering the command pallette with Ctrl+Shift+P
(Cmd+Shift+P on macOS) and running CSharp: Report an issue
command. This will open a browser window with all the necessary information related to the installed extensions, dotnet version, mono version, etc. Enter all the remaining information and hit submit. More information can be found on the wiki.
Alternatively you could visit https://github.com/OmniSharp/omnisharp-vscode/issues and file a new one.
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.
Copyright © .NET Foundation, and contributors.
The Microsoft C# extension is subject to these license terms. The source code to this extension is available on https://github.com/OmniSharp/omnisharp-vscode and licensed under the MIT license.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information see the .NET Foundation Code of Conduct.
By signing the CLA, the community is free to use your contribution to .NET Foundation projects.
This project is supported by the .NET Foundation.