v1.18.0-beta5

• Added a csharp.maxProjectFileCountForDiagnosticAnalysis setting to configure the file limit when the extension stops reporting errors for whole workspace. When this threshold is reached, the diagnostics are reported for currently opened files only. This mechanism was available in previous versions, but now can be configured. The default is 1000. (PR: #1877)
• Added initial support for C# 8. (PR: omnisharp-roslyn#1365)
• Fixed finding references to operator overloads (Contributed by @SirIntruder) (PR: omnisharp-roslyn#1371)
• Improved handling of files moving on disk (PR: omnisharp-roslyn#1368)
• Improved detection of MSBuild when multiple instances are available (Contributed by @johnnyasantoss ) (PR: omnisharp-roslyn#1349)
• Fixed a bug where the "OmniSharp" and "C# log" would steal the editor focus and hinder the user's development flow.(PR: #2828)

v1.18.0-beta4

Debugger changes:

• Added support for set next statement. Set next statement is a feature that have been available for a long time in full Visual Studio, and this brings the feature to Visual Studio Code. This feature allows developers to change what code is executed in your program. For example, you can move the instruction pointer back to re-execute a function that you just ran so you can debug into it, or you can skip over some code that you don't want to execute. To use this feature, move your cursor to the next statement you would like to execute next, and either open the editor context menu and invoke 'Set Next Statement (.NET)', or use the keyboard shortcut of Ctrl+Shift+F10 (#1753)
• Fixed evaluating string functions with interpretation in .NET Core 2.1+. Evaluation uses interpretation for conditional breakpoints, evaluating methods that take a lambda, etc (#2683)
• Many small improvements to launch.json/tasks.json generation. Highlights include a selection dialog if the workspace contains multiple launchable projects, a few simplifications to reduce the number of fields in the default launch.json, and switching the 'problem matcher' for build tasks. (PR: #2780)

v1.18.0-beta3

Merge pull request #2752 from OmniSharp/rchande-patch-11

18-beta3

v1.18.0-beta2

Merge pull request #2730 from OmniSharp/akshita31-patch-3

Remove the affected vscode package

v1.17.1

• Updated Razor language service to fix various Razor editing reliability issues. For details see https://github.com/aspnet/Razor.VSCode/releases/tag/1.0.0-alpha2.

v1.17.0

• Added preview Razor (cshtml) language service with support for C# completions and diagnostics. Please report issues with the preview Razor tooling on the aspnet/Razor.VSCode repo. To disable the preview Razor tooling set the "razor.disabled" setting to true. (PR: 2554)

• Added omnisharp.minFindSymbolsFilterLength setting to configure the number of characters a user must type in for "Go to Symbol in Workspace" command to return any results (default is 0 to preserve existing behavior). Additionally added omnisharp.maxFindSymbolsItems for configuring maximum number of items returned by "Go to Symbol in Workspace" command. The default is 1000. (PR: #2487)

• Added a command - "CSharp: Start authoring a new issue on GitHub" to enable the users to file issues on github from within the extension with helpful config information from their system.(PR: #2503)

• Fixed a bug where OmniSharp flame was red inspite of OmniSharp loading the projects without any errors.(PR: #2450)

1.17.0-beta7

Merge pull request #2624 from OmniSharp/rchande-patch-6

beta7

1.17.0-beta6

Includes the following debugger changes:

• Fix debugger shutdown crash on Linux (#2439)
• Search for PDBs in original built location (#2483)
• Fix launching the browser against an ASP.NET project that uses wildcard ('*') bindings (#2528)

v1.17.0-beta5

Merge pull request #2583 from rchande/includeRazorGrammar

Include razor grammar

v1.17.0-beta4

Merge pull request #2579 from rchande/handleEmptyTests

Handle empty tests