Merge pull request #219 from PowerShell/release/0.6.0

Prepare 0.6.0 release

Author: daviwil

CHANGELOG.md

@@ -1,26 +1,71 @@
 # PowerShell Editor Services Release History
 
+## 0.6.0
+### Thursday, May 12, 2016
+
+#### Introduced a new documentation site
+
+- We have launched a new [documentation site](https://powershell.github.io/PowerShellEditorServices/)
+  for this project on GitHub Pages.  This documentation provides both a user guide
+  and .NET API documentation pages that are generated directly from our code
+  documentation.  Check it out and let us know what you think!
+
+#### Added a new cross-editor extensibility model
+
+- We've added a new extensibility model which allows you to write PowerShell
+  code to add new functionality to Visual Studio Code and other editors with
+  a single API.  If you've used `$psISE` in the PowerShell ISE, you'll feel
+  right at home with `$psEditor`.  Check out the [documentation](https://powershell.github.io/PowerShellEditorServices/guide/extensions.html)
+  for more details!
+
+#### Support for user and system-wide profiles
+
+- We've now introduced the `$profile` variable which contains the expected
+  properties that you normally see in `powershell.exe` and `powershell_ise.exe`:
+  - `AllUsersAllHosts`
+  - `AllUsersCurrentHost`
+  - `CurrentUserAllHosts`
+  - `CurrentUserCurrentHost`
+- Each editor integration can specify what their host-specific profile filename
+  should be.  If no profile name has been specified a default of `PowerShellEditorServices_profile.ps1`
+  is used.
+- Profiles are not loaded by default when PowerShell Editor Services is used.
+  This behavior may change in the future based on user feedback.
+- Editor integrations can also specify their name and version for the `$host.Name`
+  and `$host.Version` properties so that script authors have a better idea of
+  where their code is being used.
+
+#### Other improvements
+
+- `$env` variables now have IntelliSense complete correctly (#206).
+- The debug adapter now does not crash when you attempt to add breakpoints
+  for files that have been moved or don't exist (#195).
+- Fixed an issue preventing output from being written in the debugger if you
+  don't set a breakpoint before running a script.
+- Debug adapter now doesn't crash when rendering an object for the
+  variables view if ToString throws an exception.
+
 ## 0.5.0
 ### Thursday, March 10, 2016
 
-### Support for PowerShell v3 and v4
+#### Support for PowerShell v3 and v4
 
 - Support for PowerShell v3 and v4 is now complete!  Note that for this release,
   Script Analyzer support has been disabled for PS v3 and v4 until we implement
   a better strategy for integrating it as a module dependency
 
-### Debugging improvements
+#### Debugging improvements
 
 - Added support for command breakpoints
 - Added support for conditional breakpoints
 - Improved the debug adapter startup sequence to handle new VS Code debugging features
 
-### Other improvements
+#### Other improvements
 
 - `using 'module'` now resolves relative paths correctly, removing a syntax error that
   previously appeared when relative paths were used
 - Calling `Read-Host -AsSecureString` or `Get-Credential` from the console now shows an
-  appropriate "not supported" error message instead of crashing the language service. 
+  appropriate "not supported" error message instead of crashing the language service.
   Support for these commands will be added in a later release.
 
 ## 0.4.3

README.md

@@ -19,6 +19,8 @@ across multiple editors.
   - Choice prompt support
   - Input prompt support
   - Get-Credential support (coming soon)
+- The Extension Service provides a generalized extensibility model that allows you to
+  write new functionality for any host editor that uses PowerShell Editor Services
 
 The core Editor Services library is intended to be consumed in any type of host application, whether
 it is a WPF UI, console application, or web service.  A standard console application host is included
@@ -27,12 +29,9 @@ exposes.
 
 ## Documentation
 
-Check out the following two pages for information about how to use the API and host process:
-
-- **[Using the .NET API](docs/using_the_dotnet_api.md)** - Read this if you want to use the API in your .NET application
-- **[Using the Host Process](docs/using_the_host_process.md)** - Read this if you want to use the API in a non-.NET application such as a code editor
-
-You can also read our plans for future feature development by looking at the **[Development Roadmap](https://github.com/PowerShell/PowerShellEditorServices/wiki/Development-Roadmap)**.
+Check out our **[documentation site](http://powershell.github.io/PowerShellEditorServices)** for information about
+how to use this project. You can also read our plans for future feature development by looking at the
+**[Development Roadmap](https://github.com/PowerShell/PowerShellEditorServices/wiki/Development-Roadmap)**.
 
 ## Installation
 
@@ -57,7 +56,7 @@ git submodule update
 
 We would love to incorporate community contributions into this project.  If you would like to
 contribute code, documentation, tests, or bug reports, please read our [Contribution Guide]
-(docs/contributing.md) to learn more.
+(http://powershell.github.io/PowerShellEditorServices/CONTRIBUTING.html) to learn more.
 
 ## Maintainers
 
@@ -66,4 +65,4 @@ contribute code, documentation, tests, or bug reports, please read our [Contribu
 
 ## License
 
-This project is [licensed under the MIT License](LICENSE.txt).
+This project is [licensed under the MIT License](LICENSE).

appveyor.yml

@@ -4,7 +4,7 @@ configuration: Release
 clone_depth: 10
 
 environment:
-  core_version: '0.5.0'
+  core_version: '0.6.0'
   prerelease_name: '-beta'
 
 branches: