Releases: dotnet/vscode-csharp
v1.16-beta1
Project System
-
Separated the existing "Restore Packages" option in the Command Palette into two distinct functions:
- "Restore Project" - Displays a drop-down that shows all the available projects in the solution or in the workspace. Selecting one of them would trigger a dotnet restore for the particular project.
- "Restore All Projects" - Triggers a dotnet restore for all projects in the current solution or workspace.
-
Modified the "Unresolved dependencies" prompt to restore the all the projects in the currently selected solution or workspace. (PR: #2323)
-
Added support to configure the default *.sln file loaded when opening a project with multiple *.sln files in the root. (Contributed by @janaka) (PR: #2053)
Misc
- Added a prompt to "Restart OmniSharp" when there is a change in omnisharp "path", "useGlobalMono" or "waitForDebugger" settings.(PR: #2316)
Editor
- Improved diagnostics by refreshing them when the active editor changes or the current window is focused. (PR: #2317) _(Contributed by @SirIntruder)
Testing
- Added test execution output to the output of the Run/Debug Test CodeLens. (PR: #2337, #2343, omnisharp-roslyn#1203)
- Fixed a bug where a debug session could not be started and duplicate logs were displayed after a previous one failed due to build failure. (PR: #2405, omnisharp-roslyn#1239)
v1.15.2
- Fixed a 1.30.0 regression that prevented the script project system from working on Unix-based systems (omnisharp-roslyn#1184, PR: omnisharp-roslyn#1185) (Contributed by @filipw)
- Fixed a regression that could cause the debugger to crash on Windows (#2297).
v1.15.2-beta1
- Fixed a 1.30.0 regression that prevented the script project system from working on Unix-based systems (omnisharp-roslyn#1184, PR: omnisharp-roslyn#1185) (Contributed by @filipw)
v1.15.1
- The minimum Mono version required to run OmniSharp on has been increased to 5.8.1.
v1.15.0
What's New in 1.15
Debugger
-
New features:
- Adds support for Source Link, Symbol Servers and other more advanced symbol options (#373)
- Adds launch.json option to suppress Just-In-Time compiler optimizations.
- Due to the previous two items and work from the .NET Team, it is now possible to easily debug into ASP.NET itself in projects running against .NET Core 2.1. Instructions are in the wiki.
- Adds support for pulling in environment variables from
${cwd}/Properties/launchSettings.json. This means that if you add environment variable configuration to your launchSettings.json file, they will now be used when you start your app from Visual Studio Code like they previously would be used from the command line (dotnet run), and from Visual Studio. (#2017)
-
Bug fixes:
- On Linux, this reduces the native dependencies of the debugger to match the .NET Core 2.1 runtime. The Linux .NET Core 2.1 runtime reduced its native dependencies over all the previous versions, but the debugger still had the same dependencies as .NET Core 2.0. With this fix, the debugger will now continue to work on Linux after installing the .NET Core runtime and nothing else. (#2199)
- Fixes async call stacks with the .NET Core 2.1 runtime. (#1892)
- Fixes the debugger's browser launch code when launching projects configured to use Application Insights. (2177)
Editor
- Fixed regression where the "Generate Type in New File" code action would create an empty file. (#2112, PR: omnisharp-roslyn#1143)
- Made several improvments to the display of tooltips in Signature Help. (#1940, PR: #1958)
Options
-
"omnisharp.path": This option has been updated to enable the user to specify different versions of OmniSharp, including prerelease versions. (#1909, PR: #2039)
Possible values for this option are:
<Path to the omnisharp executable>: Use a local copy of OmniSharp. The value must point directly to the OmniSharp executable. This is typically the build output directory of the omnisharp-roslyn project on the current machine, for example,C:/omnisharp-roslyn/artifacts/publish/OmniSharp.Stdio/win7-x64/OmniSharp.exe.latest: Use the latest CI build from omnisharp-roslyn.<version>: Use a specific version of OmniSharp. Example:1.29.2-beta.60
If "omnisharp.path" is not set, the defalut version of OmniSharp for the current release of C# for VS Code is used.
-
"omnisharp.useGlobalMono": This option replaces the old "omnisharp.useMono" option and controls whether or not OmniSharp will be launched with a globally-installed version of Mono. (PR: #2244)
There are three possible values:
- "auto": Automatically launch OmniSharp with
monoif version 5.2.0 or greater is available on the PATH. - "always": Always launch OmniSharp with
mono. If version 5.2.0 or greater is not available on the PATH, an error will be printed. - "never": Never launch OmniSharp on a globally-installed Mono.
- "auto": Automatically launch OmniSharp with
-
It is now possible to suppress the "Some projects have trouble loading" popup using the
omnisharp.disableMSBuildDiagnosticWarningoption. (#2110
Project System
-
Several common globbing patterns are now excluded by default when OmniSharp scans for
*.csproj,*.cake, or*.csxfiles to load. The deafault patterns are**/node_modules/**/*,**/bin/**/*,**/obj/**/*,**/.git/**/*. (omnisharp-roslyn#896, PR: omnisharp-roslyn#1161) (Contributed by @filipw) -
The list of globbing patterns that are excluded by OmniSharp can be customized in an
omnisharp.jsonfile list so.{ "systemExcludeSearchPatterns": [ "**/test/**/*" ], "excludeSearchPatterns": [ "**/local/**/*" ] }For more details on configuring OmniSharp see Configuration Options at the omnisharp-roslyn repo. (omnisharp-roslyn#896, PR: omnisharp-roslyn#1161) (Contributed by @filipw)
-
Improved handling of projects with XAML files. (#2173, PR: omnisharp-roslyn#1157)
-
MSBuild is now properly located on Windows for Visual Studio 2017 previews. (omnisharp-roslyn#1166) (Contributed by @rainersigwald)
Scripting
-
It is now possible to define the default target framework for C# scripts in an
omnisharp.jsonfile.{ "script": { "defaultTargetFramework": "netcoreapp2.0" } }(PR: omnisharp-roslyn#1154) (Contributed by @filipw)
Status Bar
-
Splits the OmniSharp status bar item into two parts, both of which appear on the left side of VS Code's status bar and have specific responsibilities. (#2146, PR: #2133)
- OmniSharp Server info:
- Displays the current state of the OmniSharp server, such as Downloading, Installing, etc. The flame icon is green when the server is initialized and running properly, or red if there is an error.
- Selected Project info:
- Displays the name of the selected project regardless of the currently active document.
- If a project is already selected, it displays the name of the selected project. Clicking on it displays a menu to switch to other projects in the workspace.
- If there are multiple possible launch targets, it displays 'Select Project'. Clicking on it displays a menu to select one.
- OmniSharp Server info:
Testing
- Added "debug all tests" and "run all tests" to the CodeLens that appears above test classes to allow running or debugging all tests in a class. (#420, PRs: #1961, omnisharp-roslyn#1089
Misc
v1.15.0-beta6
- Fixed issues with installing and launching OmniSharp on macOS/Linux introduced in beta5.
- Added "omnisharp.useGlobalMono" option that replaces "omnisharp.useMono". This is respected at launch time when using "omnisharp.path" to target a specific version or the latest version of OmniSharp.
v1.15.0-beta5
Merge pull request #2249 from TheRealPiotrP/dev/therealpiotrp/asyncFile Fix for async-file issue
v1.15.0-beta4
1.15.0-beta4 (#2143)
v1.15.0-beta3
Refactoring internal logging infrastructure
v1.15.0-beta2
Specify OmniSharp Version
Enables the use of pre-release builds of Omnisharp. Downloading a pre-release build of Omnisharp allows the C# extension for VS Code to use features that have been merged into the "master" branch of omnisharp-roslyn(https://github.com/OmniSharp/omnisharp-roslyn) but that have not been officially released
- Adds support to use the "omnisharp.path" option to download a specific copy of OmniSharp. The possible values for this option are:
- Some absolute path - Use a local copy of OmniSharp. The value must point to a directory which contains OmniSharp, typically a user's build output directory for the OmniSharp-Roslyn project. Example: C:\omnisharp-roslyn\artifacts\publish\OmniSharp.Stdio\win7-x64\OmniSharp.exe.
- "latest" - Use the latest CI build
version- Use a specific version of OmniSharp. Example:1.29.2-beta.60
Editor
- Adds "Run All Tests" and "Debug All Tests" Code Lenses to run/debug all of the tests in a class