Merge pull request #2600 from gregg-miskelly/merge_release

Merge release->master

Author: gregg-miskelly

CHANGELOG.md

@@ -6,6 +6,8 @@
   * Loss of HTML completions following C# less than (`<`) operator
   * Error squiggles misaligned for expressions near the start of a new line
   * Leaving Razor files open for a significant period of time results in loss of Razor C# tooling on macOS
+* There currently is no completion support for package references in csproj files. ([#1156](https://github.com/OmniSharp/omnisharp-vscode/issues/1156))
+  * As an alternative, consider installing the [MSBuild Project Tools](https://marketplace.visualstudio.com/items?itemName=tintoy.msbuild-project-tools) extension by @tintoy.
 
 ## 1.17.0 (Not yet released)
 
@@ -15,13 +17,12 @@
 
 * Added a command - "CSharp: Start authoring a new issue on GitHub" to enable the users to file issues on github from within the extension with helpful config information from their system.(PR: [#2503](https://github.com/OmniSharp/omnisharp-vscode/pull/2503))
 
-* Fixed a bug where OmniSharp flame was red inspite of OmniSharp loading the projects without any errors.(PR: [#2450](https://github.com/OmniSharp/omnisharp-vscode/pull/2540))
-
-## Known Issues in 1.16.0
+## 1.16.2 (October 3, 2018)
+* Update extension to handle upcoming breaking change to launch.json configurations in VS Code 1.28. (PR: [#2558](https://github.com/OmniSharp/omnisharp-vscode/pull/2558))
+* Fixed a bug where OmniSharp flame was red in spite of OmniSharp loading the projects without any errors. (PR: [#2450](https://github.com/OmniSharp/omnisharp-vscode/pull/2540))
+* Fixed launch.json `envFile` option on Windows. (PR: [#2560](https://github.com/OmniSharp/omnisharp-vscode/pull/2560))
+* Fixed a problem with tracking virtual documents from other providers. (PR: [#2562](https://github.com/OmniSharp/omnisharp-vscode/pull/2562))
 
-* There currently is no completion support for package references in csproj files. ([#1156](https://github.com/OmniSharp/omnisharp-vscode/issues/1156))
-  * As an alternative, consider installing the [MSBuild Project Tools](https://marketplace.visualstudio.com/items?itemName=tintoy.msbuild-project-tools) extension by @tintoy.
-  
 ## 1.16.0 (September 10, 2018)
 
 #### Project System

README.md

@@ -20,6 +20,12 @@ The C# extension is powered by [OmniSharp](https://github.com/OmniSharp/omnishar
 * [Documentation](https://code.visualstudio.com/docs/languages/csharp)
 * [Video Tutorial compiling with .NET Core](https://channel9.msdn.com/Blogs/dotnet/Get-started-VSCode-Csharp-NET-Core-Windows)
 
+### What's New in 1.16.2
+* Update extension to handle upcoming breaking change to launch.json configurations in VS Code 1.28.
+* Fixed launch.json `envFile` option on Windows
+* Fixed a bug where OmniSharp flame was red inspite of OmniSharp loading the projects without any errors.
+* Fixed a problem with tracking virtual documents from other providers
+
 ### What's New in 1.16.0
 
 * Debugger support for launching with environment variables stored in a separate file from launch.json via a new `envFile` option.