|
1 | 1 | # PowerShell Editor Services Release History
|
2 | 2 |
|
| 3 | +## 0.6.0 |
| 4 | +### Thursday, May 12, 2016 |
| 5 | + |
| 6 | +#### Introduced a new documentation site |
| 7 | + |
| 8 | +- We have launched a new [documentation site](https://powershell.github.io/PowerShellEditorServices/) |
| 9 | + for this project on GitHub Pages. This documentation provides both a user guide |
| 10 | + and .NET API documentation pages that are generated directly from our code |
| 11 | + documentation. Check it out and let us know what you think! |
| 12 | + |
| 13 | +#### Added a new cross-editor extensibility model |
| 14 | + |
| 15 | +- We've added a new extensibility model which allows you to write PowerShell |
| 16 | + code to add new functionality to Visual Studio Code and other editors with |
| 17 | + a single API. If you've used `$psISE` in the PowerShell ISE, you'll feel |
| 18 | + right at home with `$psEditor`. Check out the [documentation](https://powershell.github.io/PowerShellEditorServices/guide/extensions.html) |
| 19 | + for more details! |
| 20 | + |
| 21 | +#### Support for user and system-wide profiles |
| 22 | + |
| 23 | +- We've now introduced the `$profile` variable which contains the expected |
| 24 | + properties that you normally see in `powershell.exe` and `powershell_ise.exe`: |
| 25 | + - `AllUsersAllHosts` |
| 26 | + - `AllUsersCurrentHost` |
| 27 | + - `CurrentUserAllHosts` |
| 28 | + - `CurrentUserCurrentHost` |
| 29 | +- Each editor integration can specify what their host-specific profile filename |
| 30 | + should be. If no profile name has been specified a default of `PowerShellEditorServices_profile.ps1` |
| 31 | + is used. |
| 32 | +- Profiles are not loaded by default when PowerShell Editor Services is used. |
| 33 | + This behavior may change in the future based on user feedback. |
| 34 | +- Editor integrations can also specify their name and version for the `$host.Name` |
| 35 | + and `$host.Version` properties so that script authors have a better idea of |
| 36 | + where their code is being used. |
| 37 | + |
| 38 | +#### Other improvements |
| 39 | + |
| 40 | +- `$env` variables now have IntelliSense complete correctly (#206). |
| 41 | +- The debug adapter now does not crash when you attempt to add breakpoints |
| 42 | + for files that have been moved or don't exist (#195). |
| 43 | +- Fixed an issue preventing output from being written in the debugger if you |
| 44 | + don't set a breakpoint before running a script. |
| 45 | +- Debug adapter now doesn't crash when rendering an object for the |
| 46 | + variables view if ToString throws an exception. |
| 47 | + |
3 | 48 | ## 0.5.0
|
4 | 49 | ### Thursday, March 10, 2016
|
5 | 50 |
|
6 |
| -### Support for PowerShell v3 and v4 |
| 51 | +#### Support for PowerShell v3 and v4 |
7 | 52 |
|
8 | 53 | - Support for PowerShell v3 and v4 is now complete! Note that for this release,
|
9 | 54 | Script Analyzer support has been disabled for PS v3 and v4 until we implement
|
10 | 55 | a better strategy for integrating it as a module dependency
|
11 | 56 |
|
12 |
| -### Debugging improvements |
| 57 | +#### Debugging improvements |
13 | 58 |
|
14 | 59 | - Added support for command breakpoints
|
15 | 60 | - Added support for conditional breakpoints
|
16 | 61 | - Improved the debug adapter startup sequence to handle new VS Code debugging features
|
17 | 62 |
|
18 |
| -### Other improvements |
| 63 | +#### Other improvements |
19 | 64 |
|
20 | 65 | - `using 'module'` now resolves relative paths correctly, removing a syntax error that
|
21 | 66 | previously appeared when relative paths were used
|
22 | 67 | - Calling `Read-Host -AsSecureString` or `Get-Credential` from the console now shows an
|
23 |
| - appropriate "not supported" error message instead of crashing the language service. |
| 68 | + appropriate "not supported" error message instead of crashing the language service. |
24 | 69 | Support for these commands will be added in a later release.
|
25 | 70 |
|
26 | 71 | ## 0.4.3
|
|
0 commit comments