v1.4.0-beta3

This release updates to v1.9-beta13 of OmniSharp, which fixes the data returned by Roslyn workspace events that are forwarded from the OmniSharp server. This may improve performance with larger projects containing many diagnostics.

v1.3.0

What's New in 1.3

• Support for Unity and Mono development on macOS and Linux has been restored! This release brings back support for the Mono version of OmniSharp, which is used to provide much better support for .csproj/.sln projects. Please note that Mono version 4.0.1 or newer is required.
• Generation of tasks.json and launch.json files can now properly handle nested projects. #170
• New UI that makes it easy to select a process ID when attaching the debugger to another process. Note: If you have an existing launch.json file, you can re-generate it by deleting the file, closing your workspace in Visual Studio Code and opening it again. Or, you can open the launch.json file and change the processId value to "${command.pickProcess}".
• Support for debugging in .cshtml files. To enable this, add a sourceFileMap entry to your launch.json with the following content: "sourceFileMap": { "/Views": "${workspaceRoot}/Views" }
• Support for conditional breakpoints
• New support for changing variable values in the debugger! To try this, just right-click on the variable name and select 'Set Value'. Note: To properly support this feature, we've changed the display of variable type names in the debugger to a shortened form. The full type name can be viewed by hovering over the name with the mouse.
• New configuration option to enable stepping into properties and operators.
• Duplicate warnings and errors should no longer accumulate in Unity projects #447

v1.3.0-beta2

This release fixes several issues:

• Launch.json and tasks.json files are properly generated for nested projects.
• Duplicate diagnostics should no longer be reported.
• Diagnostics should be refreshed after packages are restored.

v1.3.0-beta1

This release adds support for dual OmniSharps, depending on the type of project being opened.

• For project.json, the .NET Core version of OmniSharp will be acquired and launched.
• For .csproj/.sln (on Windows), the .NET 4.5.1 version of OmniSharp will be acquired and launched.
• For .csproj/.sln (on macOS/Linux), the Mono version of OmniSharp will be acquired and launched. Note that this requires mono version 4.0.1 or later.

v1.2.2

Fixes OmniSharp installation on RHEL

v1.2.1

Merge pull request #520 from OmniSharp/master

Merge master -> release

v1.2.0

What's new in 1.2:

• Support for new Linux versions: Ubuntu 16.04, Fedora 23, openSUSE 13.2, and Oracle Linux 7.1
• Enhanced debug console output: module loads are now output, and there are launch.json options for controlling what is output
• Source file checksum support for breakpoints. This ensures that the debugger only sets breakpoints in code that exactly matches the open document.
• Support for editing the value of variables in the watch and locals window (requires VS Code 1.3)

v1.1.7

Add initial support (partially working) for .csproj-based projects.

v1.1.6

1.1.6 includes the work from 1.1.5, plus these additions:

• Provides primitives needed for Docker debugging
• Resolves an issue where myget.org feeds could be hit while downloading the debugger

v1.1.5

This is the first 1.1-based C# extension released to the gallery. Here is what is new in v1.1:

• Preliminary support for dotnet test
• Fix for OmniSharp installation problems on networks with an http proxy
• Debugger support for an external console
• Debugger support for environment variables
• Support for debugging .NET Core 1.0.0 post RC2 builds
• Automatic web vs. console debugger configuration detection
• Detach support
• Fix expression evaluation errors when referencing assemblies which aren't currently loaded
• Fix expression evaluation on Win7