v1.9.0

What's New in 1.9

Unit Testing

• Support added for running and debugging unit tests in .csproj-based .NET Core projects. (#1100)

Debugger

• Arch Linux change: Before, the debugger would automatically use the Ubuntu 16 debugger on Arch. Now we require the debugger to be explicitly set. See https://aka.ms/vscode-csext-arch for more information.
• Several bug fixes that addressed problems with launch (#1335, #1336)
• Fixed several pipeTransport issues including introducing a new quoteArgs option (#1318), and fixing attach with Docker (#1369)
• Fix issue where VS Code would incorrectly display threads as paused (#1317)
• Added new 'csharp.fallbackDebuggerLinuxRuntimeId' configuration setting to control the version of the debugger used on Linux (#1361).
• Added a new clr debugging type in launch.json to enable debugging for Azure scenarios. That type is limited to Windows Desktop CLR, 64-bit processes, and only supports the Portable PDB debug format.
• Added support for the launch.json editor's 'Add Configuration' button (#1024)

Project System

• Properly handle package references with version ranges in .csproj (PR: omnisharp-roslyn#814)
• Fix regression with MSBuild project system where a project reference and a binary reference could be added for the same assembly, causing ambiguity errors (omnisharp-roslyn#795, PR: omnisharp-roslyn#815)
• If VS 2017 is on the current machine, use the MSBuild included with VS 2017 for processing projects. (#1368, PR: omnisharp-roslyn#818OmniSharp/omnisharp-roslyn#818)
• Fixed null reference exception in DotNetProjectSystem when project reference is invalid (PR: omnisharp-roslyn#797)

Improved OmniSharp Settings

• Added support for global omnisharp.json file (omnisharp-roslyn#717, PR: omnisharp-roslyn#809) (Contributed by @filipw)

  This file can appear in one of the following locations:

  • Windows: %APPDATA%\OmniSharp\omnisharp.json
  • macOS/Linus: ~/.omnisharp/omnisharp.json

• Watch local and global omnisharp.json files for changes while OmniSharp is running. Currently, this only works for formatting options. (PR: omnisharp-roslyn#804)(Contributed by @filipw)

• New 'omnisharp.waitForDebugger' setting to make it easier to debug the OmniSharp server itself. (PR: #1370)

Other Updates and Fixes

• Improvements made to project.json package completion experience. (#1338)
• Diagnostics are no longer created for hidden diagnostics, addressing the problem of "Remove Unnecessary Usings" spam in the Problems pane. (#1231)
• Improved the extension's runtime dependency download logic to skip re-downloading packages that were already successfully downloaded and installed.
• Assets for building and debugging are now always generated with POSIX style paths. (#1354)
• Don't offer to generate tasks.json if build task already exists. (PR #1363) (Contributed by @eamodio)

Known Issues in 1.9.0

• When opening a .csproj-based .NET Core project in VS Code, the C# extension will not activate until a C# file is opened in the editor. (#1150)
• There currently is no completion support for package references in csproj files. (#1156)