Skip to content

v1.10.0

Choose a tag to compare

@DustinCampbell DustinCampbell released this 25 May 19:09
· 6733 commits to release since this release

What's New in 1.10

Completion List

  • Several improvements to the completion list! (All contributed by @filipw with PR omnisharp-roslyn#840)
    • Attributes are completed properly without the 'Attribute' suffix. (#393)
    • Named parameters now appear in the completion list. (#652)
    • Object initializer members now appear in the completion list. (#260)
    • Completion appears within XML doc comment CREFs.
    • Initial support for completion on 'override' and 'partial' keywords. (#1044)
  • New VS Code completion item glyphs (e.g. struct, event, etc.) are supported. (PR: #1472) (Contributed by @dopare)
  • Updated completion to use same commit characters as Visual Studio. Completion should now complete as non-identifier characters are typed. (#1487, #1491, PR: #1494)

Project System

  • Project references to projects located outside of the current workspace directory are now loaded and processed. (#963, PR: omnisharp-roslyn#832)
  • OmniSharp now loads .NET Core projects using the SDKs included with the .NET Core SDK appropriate for that project, if they're installed on the machine. (#1438, omnisharp-roslyn#765, PR: omnisharp-roslyn#847)
  • Options can now be set in an omnisharp.json to specify the Configuration (e.g. Debug) and Platform (e.g. AnyCPU) that MSBuild should use. (omnisharp-roslyn#202, PR: omnisharp-roslyn#858) (Contributed by @nanoant)
  • Fixed issue where a package reference would be reported as an unresolved dependency if the reference differed from the intended dependency by case (PR: #861)
  • Cleaned up unresolved dependency detection in OmniSharp and added logging to help diagnose project issues. (#1272, PR: #861)

Scripting

Unit Testing

  • MSTest support added (#1482, PRs: #1478, omnisharp-roslyn#856) (Contributed by @AbhitejJohn)
  • Add support for NUnit Test Adapter. (#1434, PR: omnisharp-roslyn#834)
  • Files are saved before running or debugging tests to ensure that recent unsaved changes are included in test runs. (#1473, PR: #1493)
  • Tests that define display names are now run properly. (#1426, PR: omnisharp-roslyn#833)
  • Tests with similar names are no longer incorrectly run together when one of them is clicked. (#1432, PR: omnisharp-roslyn#833)
  • Improve response from running/debugging tests to include output from build and test summary. (#419, #455, PRs: #1436, #1486)
  • Added csharp.unitTestDebugingOptions setting to pass launch.json-style debug options (example: justMyCode) when unit test debugging.

Debugger

  • Resolves crash on OSX when the target process loads an embedded PDB (#1456). This commonly affects users trying to debug XUnit tests.
  • Enhanced exception peek display to provide additional exception properties.

Other Updates and Fixes

  • New csharp.suppressHiddenDiagnostics setting that can be set to true to display hidden diagnostics, such as 'unnecessary using directive'. (#1429, PR: #1435) (Contributed by @cruz82)
  • Fix issue causing several code snippets to not be available. (#1459, PR: #1461) (Contributed by @shaunluttin)
  • Ensure the 'Generate Assets for Build and Debug' command can cause the extension to activate. (PR: #1470)
  • The OmniSharp process is now correctly terminated on Unix when the 'Restart OmniSharp' command is invoked. (#1445, PR: #1466)
  • Added new RoslynExtensions option to allow specifying a set of assemblies in an omnisharp.json file that OmniSharp will look in to find Roslyn extensions to load. (PR: omnisharp-roslyn#848) (Contributed by @filipw)

Known Issues in 1.10.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)
  • .NET Core SDK 2.0-preview2 is not yet supported. (#1495)