v0.6.0

Introduced a new documentation site

• We have launched a new documentation site
  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
  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.