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)

v1.5-beta8

This includes the latest changes in master:

• Everything from the v1.5-future-preview1 build
• Feature to check the ID_LIKE field in /etc/os-release to allow the debugger to install on more Linux distros. (#890)
• Properly escape ampersands in Windows file names when launch OmniSharp. (#909)

v1.5-future-preview1

This release includes several changes that have not yet been merged into master in order to let people try them out. The key changes are:

• Running OmniSharp on an embedded Mono runtime. This should greatly increase the breadth of Linux distributions that the extension will work with. Note that this only affects OmniSharp, which provides editing features like auto complete, find all references, rename, etc. The debugger is still limited to a smaller set of Linux distributions.
• Initial support for MSBuild-based .NET Core projects. There is still a great deal of work to support the new MSBuild-based .NET Core projects properly, but OmniSharp can now understand and load them properly.
• Better performance via concurrent communication with OmniSharp. Previously, communication with the OmniSharp server was handled serially. This meant that long-running operations (such as gathering all diagnostics for a project) could cause the entire system to wait. Now communication is better-prioritized: high priority work (such as buffer changes due to typing) are handled serially and long-running operations are allowed to run and respond when they're ready.
• Initial C# 7 support. OmniSharp has been updated to the latest Roslyn 2.0.0 bits, enabling C# 7.

v1.5-beta7

• Update debugger acquisition to use new package management system. (#873)
• Fix OmniSharp launch on Mono. (#874)
• Add new omnisharp.projectLoadTimeout setting to control the amount of time that the C# extension will wait for the OmniSharp server to launch before timing out. (#880)

v1.5-beta6

• Added csharp.suppressDotnetRestoreNotification setting to allow the 'dotnet restore' notifications to be suppressed. (#193, #257, #845)
• Tweak ctor code snippet to remove unnecessary space and insert tabs like other code snippets (#849)

v1.5-beta5

• Introduce new runtime dependency acquisition experience

v1.5-beta4

• Fix issue where not all errors/warnings would be displayed. (#812)