v1.12.0-beta1

Debugger

• Update debugger to run itself on .NET Core 2.0-preview2 (target app can still use .NET Core 1.x). This allows the debugger to run on more Linux distributions, and it allows there to be a single debugger package for all supported Linux distributions.
• Fix issue where the call stack may be empty when stepping quickly (#1575)

Other Updates and Fixes

• Automatically activate the extension when opening workspaces that contain any .csproj, .sln, or .csx files (#1375, #1150, PR: #1592))

v1.11.0

What's New in 1.11

Completion List

• No longer trigger completion when a '<' character is typed. (#1521, PR: #1530)
• Completion list no longer triggers on space in contexts where a lambda expression could be typed. (#1524, PR: #1548)

Project System

• Fixed support for the latest .NET Core 2.0 preview. (#1566)

Other Updates and Fixes

• Improved download speeds for OmniSharp and Mono dependencies.
• Allow the ".NET: Restore Packages" command to run on projects targeting full framework. (#1507, PR: #1545) (contributed by @adamhartford)

Known Issues in 1.11

• 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)

v1.11.0-beta4

• Fixes another issue with .NET Core 2.0 Preview 2.0 on OSX/Linux (#1566)
• Adds URLs for OmniSharp and Mono that are behind an Azure CDN to speed up downloads.

v1.11.0-beta3

• Fix .NET Core 2.0-preview2 support on OSX/Linux (#1495)

v1.11.0-beta2

• Fix .NET Core 2.0-preview2 support on Windows (#1495)

v1.11.0-beta1

• No longer trigger completion when a '<' character is typed. (#1521, PR: #1530)
• Completion list no longer triggers on space in contexts where a lambda expression could be typed. (#1524, PR: #1548)
• Allow the ".NET: Restore Packages" command to run on projects targeting full framework. (#1507, PR: #1545) (contributed by @adamhartford)

v1.10.0

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

• Support Metadata as Source for Go To Definition in CSX files. (omnisharp-roslyn#755, PR: (omnisharp-roslyn#829) (Contributed by @filipw)

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)

v1.10.0-beta4

• Resolves crash on OSX when the target process loads an embedded PDB (#1456). This commonly affects users trying to debug XUnit tests.
• When running or debugging unit tests - make sure all files are saved first
• Add commit character for completion

v1.10.0-beta3

• New VS Code completion item glyphs (e.g. struct, event, etc.) are supported. (PR: #1472) (Contributed by @dopare)
• 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)
• MSTest support added (#1482, PRs: #1478, omnisharp-roslyn#856) (Contributed by @AbhitejJohn)
• Improve response from running/debugging tests to include output from build and test summary. (#419, #455, PRs: #1436, #1486)
• 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)

v1.10.0-beta2

• 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)
• 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)