v1.6-beta6

• Fix (again!) for UriFormatException that can happen during project load with .NET Core csproj projects on Windows. (#1050)
• Fix problem where errors would be reported in newly-created .NET Core web project. (#1049)

v1.6-beta5

• Fix for UriFormatException that can happen during project load with .NET Core csproj projects on Windows. (#1045)
• Better support for cross-targeting projects.

v1.6-beta4

• Enable debugger support for Arch Linux (#564)
• Support for latest .NET Core .csproj projects updates. (omnisharp-roslyn#705)
• Roslyn scripting support in CSX files! (omnisharp-roslyn#659) (Contributed by @filipw)
• Support for running/debugging NUnit tests (#996) (Contributed by @HexWrench)
• Fix signature help display for constructors. (#36) (Contributed by @filipw)
• Tons of great syntax highlighting fixes and support! (All contributed by @ivanz)
  • Fix for field declarations. (#757)
  • Fix for generic types with multiple type parameters. (#960)
  • Proper support for interpolated strings (verbatim and non-verbatim). (#852)
  • Fix for multi-line properties. (#854)
  • Fixes for events, nested type references (e.g. Root.IInterface<Something.Nested>), variable declarations, nested classes, and fields spanning multiple lines

v1.6-beta3

• Update the debugger to internally run on .NET Core 1.1. Which hopefully lights up new Linux distros - Fedora 24, Ubuntu 16.10, and openSUSE 42.1
• Add warning when installing on Windows x86
• Add error when installing on OSX and OpenSSL symlinks are missing

v1.6-beta2

• Properly support <NoWarn> in MSBuild projects and specifically ignore the CS1701 warning in .NET Core MSBuild projects (#967)
• Fix global.json-based project search to also the top-level folders specified by the "projects" property and not just their children. (#904 and #962)
• Fix exception thrown when sending /autocomplete request to OmniSharp server in location where no completion items are available (#980)
• Improve display of hover tool tips for nested classes (#394) (Contributed by @filipw)
• Fix spacing in hover tool tips around <paramref/> in XML doc comments (#672) (Contributed by @filipw)

v1.5.3

• Properly respect the VS Code http.proxyStrictSSL option when set. (#957)

v1.6-beta1

• Add omnisharp.maxProjectResults setting to control the maximum number of projects to display in the 'Select Project' dropdown. The default is 250. (#875) (Contributed by @filipw)
• Properly respect the VS Code http.proxyStrictSSL option when set. (#957)

v1.5.2

• Ensure diagnostics are cleared in files when they are no longer needed. (#858)
• Enqueue requests for diagnostics in visible editors when the extension starts up. (#843)
• Provide fallback URLs for debugger downloads. (#930)
• Properly require .NET Framework 4.6 in the OmniSharp.exe.config file to ensure that the user is displayed a dialog on Windows machines that don't have .NET Framework 4.6 installed. (#937)
• Fix issue with installing on non-English installations of Windows. (#938)
• Display platform information when acquiring runtime dependencies. (#948)

v1.5.1

• Fix to properly support http.proxy and http.proxyStrictSSL settings. (#930)

v1.5.0

What's New in 1.5

Initial support for C# 7

• New C# 7 features like pattern-matching and tuples are now supported in VS Code editor. Note: To use tuples, you will need a reference to this NuGet package.

Initial support for CSProj .NET Core Projects

• With the .NET Core SDK moving to embrace MSBuild and .csproj files over project.json, we've made sure the C# extension can handle the new format. This support is preliminary and there are still several features coming to smooth out the experience.

Broader OS Support for C# Code Editing

• This release dramatically changes the runtime that OmniSharp runs on, which allows it to be run an many more operating systems than before:
  • Windows: OmniSharp runs on the installed .NET Framework. In addition, OmniSharp now runs on 32-bit Windows!
  • macOS/Linux: OmniSharp runs on a custom embedded Mono runtime. Note: Mono does not need to be installed on the system for this to work.

Debugger

• Remote debugging is now supported for attach by using the pipeTransport launch.json option.
• Resolved issue with setting breakpoints when there are multple files with the same name (e.g. two 'Program.cs' files).

New Dependency Acquisition System

• This improves the acquisition and reliability of platform-specific OmniSharp and debugger dependencies.

New Settings

Several new settings have been added:

• csharp.suppressDotnetRestoreNotification: Suppress the notification window to perform a 'dotnet restore' when dependencies can't be resolved.
• omnisharp.projectLoadTimeout: The time Visual Studio Code will wait for the OmniSharp server to start. Time is expressed in seconds. (Contributed by @wjk)

Colorizer

• A new unit testing framework for testing the colorizer grammer (#742) (Contributed by @ivanz)
• Single-line comments after preprocessor directives (#762) (Contributed by @damieng)

Performance

• Major improvements have been made to editor performance. The communication with the OmniSharp server has been rewritten to allow long-running operations (such as gathering all errors and warnings) to queue while high priority operations (such as text buffer changes) run serially. (#902) (Thanks to @david-driscoll for his help with this change!)

Other Improvements

• The prompt to generate assets for building and debugging can now be dismissed for a workspace permanently. In addition, a new dotnet.generateAssets command has been added to force regeneration of the assets. (#635)
• Fix "running forever" issue for folder with multple .NET Core projects. (#735) (Contributed by @eamodio)
• ctor snippet is now more consistent with other code snippets. (#849) (Contibuted by @Eibx)
• Ampersands in file paths are now properly escaped on Windows (#909) (Contributed by @filipw)