Skip to content

Commit 654d667

Browse files
committed
Bump version to 0.6.0, update CHANGELOG.md
1 parent 9d6c724 commit 654d667

File tree

2 files changed

+40
-1
lines changed

2 files changed

+40
-1
lines changed

CHANGELOG.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,44 @@
11
# vscode-powershell Release History
22

3+
## 0.6.0
4+
### Thursday, May 12, 2016
5+
6+
#### Added a new cross-editor extensibility model
7+
8+
- We've added a new extensibility model which allows you to write PowerShell
9+
code to add new functionality to Visual Studio Code and other editors with
10+
a single API. If you've used `$psISE` in the PowerShell ISE, you'll feel
11+
right at home with `$psEditor`. Check out the [documentation](https://powershell.github.io/PowerShellEditorServices/guide/extensions.html)
12+
for more details!
13+
14+
#### Support for user and system-wide profiles
15+
16+
- We've now introduced the `$profile` variable which contains the expected
17+
properties that you normally see in `powershell.exe` and `powershell_ise.exe`:
18+
- `AllUsersAllHosts`
19+
- `AllUsersCurrentHost`
20+
- `CurrentUserAllHosts`
21+
- `CurrentUserCurrentHost`
22+
- In Visual Studio Code the profile name is `Microsoft.VSCode_profile.ps1`.
23+
- `$host.Name` now returns "Visual Studio Code Host" and `$host.Version` returns
24+
the version of the PowerShell extension that is being used.
25+
26+
#### Other improvements
27+
28+
- IntelliSense for static methods and properties now works correctly. If you
29+
type `::` after a type such as `[System.Guid]` you will now get the correct
30+
completion results. This also works if you press `Ctrl+Space` after the `::`
31+
characters.
32+
- `$env` variables now have IntelliSense complete correctly.
33+
- The debug adapter now does not crash when you attempt to add breakpoints
34+
for files that have been moved or don't exist.
35+
- Fixed an issue preventing output from being written in the debugger if you
36+
don't set a breakpoint before running a script.
37+
38+
#### New configuration settings
39+
40+
- `powershell.scriptAnalysis.settingsPath`: Specifies the path to a PowerShell Script Analyzer settings file. Use either an absolute path (to override the default settings for all projects) or use a path relative to your workspace.
41+
342
## 0.5.0
443
### Thursday, March 10, 2016
544

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "PowerShell",
33
"displayName": "PowerShell",
4-
"version": "0.5.0",
4+
"version": "0.6.0",
55
"publisher": "ms-vscode",
66
"description": "Develop PowerShell scripts in Visual Studio Code!",
77
"engines": {

0 commit comments

Comments
 (0)