|
1 | 1 | # vscode-powershell Release History
|
2 | 2 |
|
| 3 | +## 0.5.0 |
| 4 | +### Thursday, March 10, 2016 |
| 5 | + |
| 6 | +#### Support for PowerShell v3 and v4 |
| 7 | + |
| 8 | +- Support for PowerShell v3 and v4 is now complete! Note that for this release, |
| 9 | + Script Analyzer support has been disabled for PS v3 and v4 until we implement |
| 10 | + a better strategy for integrating it as a module dependency |
| 11 | + |
| 12 | +#### Debugging improvements |
| 13 | + |
| 14 | +- Added support for command breakpoints |
| 15 | +- Added support for conditional breakpoints |
| 16 | +- Improved the debug adapter startup sequence to handle new VS Code debugging features |
| 17 | + |
| 18 | +#### Other improvements |
| 19 | + |
| 20 | +- Added a preview of a possible project template for PowerShell Gallery modules in |
| 21 | + the `examples` folder. Includes a PSake build script with Pester test, clean, |
| 22 | + build, and publish tasks. Check it out and give your feedback on GitHub! |
| 23 | +- `using 'module'` now resolves relative paths correctly, removing a syntax error that |
| 24 | + previously appeared when relative paths were used |
| 25 | +- Calling `Read-Host -AsSecureString` or `Get-Credential` from the console now shows an |
| 26 | + appropriate "not supported" error message instead of crashing the language service. |
| 27 | + Support for these commands will be added in a later release. |
| 28 | + |
| 29 | +#### New configuration settings |
| 30 | + |
| 31 | +- `powershell.useX86Host`: If true, causes the 32-bit language service to be used on 64-bit Windows. On 32-bit Windows this setting has no effect. This setting does not affect the debugger which has its own architecture configuration. |
| 32 | + |
3 | 33 | ## 0.4.1
|
4 |
| -### Wednesday, February 17, 2016 |
| 34 | +#### Wednesday, February 17, 2016 |
5 | 35 |
|
6 | 36 | - Updated PSScriptAnalyzer 1.4.0 for improved rule marker extents
|
7 | 37 | - Added example Pester task for running tests in the examples folder
|
|
0 commit comments