Skip to content

Release 0.5.0 #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 10, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,44 @@
# vscode-powershell Release History

## 0.5.0
### Thursday, March 10, 2016

#### 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

- Added support for command breakpoints.

Hover over the Debug workspace's 'Breakpoints' list header and click the 'Add'
button then type a command name (like `Write-Output`) in the new text box that
appears in the list.

- Added support for conditional breakpoints.

Right click in the breakpoint margin to the left of the code editor and click
'Add conditional breakpoint' then enter a PowerShell expression in the text box
that appears in the editor.

#### Other improvements

- Added a preview of a possible project template for PowerShell Gallery modules in
the `examples` folder. Includes a PSake build script with Pester test, clean,
build, and publish tasks. See the `examples\README.md` file for instructions.
Check it out and give your feedback on GitHub!
- `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.
Support for these commands will be added in a later release.

#### New configuration settings

- `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.

## 0.4.1
### Wednesday, February 17, 2016

Expand Down
7 changes: 4 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
{
"name": "PowerShell",
"displayName": "PowerShell",
"version": "0.4.1",
"version": "0.5.0",
"publisher": "ms-vscode",
"description": "Develop PowerShell scripts in Visual Studio Code!",
"engines": {
"vscode": "^0.10.8"
"vscode": "^0.10.10"
},
"license": "SEE LICENSE IN LICENSE.txt",
"homepage": "https://github.com/PowerShell/vscode-powershell/blob/master/README.md",
Expand Down Expand Up @@ -119,7 +119,8 @@
"program": "bin/Microsoft.PowerShell.EditorServices.Host.x86.exe"
},
"args": [
"/debugAdapter"
"/debugAdapter",
"/logLevel:Verbose"
],
"configurationAttributes": {
"launch": {
Expand Down
5 changes: 0 additions & 5 deletions src/main.ts
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,6 @@ export function activate(context: vscode.ExtensionContext): void {
],

__electricCharacterSupport: {
brackets: [
{ tokenType: 'delimiter.curly.ts', open: '{', close: '}', isElectric: true },
{ tokenType: 'delimiter.square.ts', open: '[', close: ']', isElectric: true },
{ tokenType: 'delimiter.paren.ts', open: '(', close: ')', isElectric: true }
],
docComment: { scope: 'comment.documentation', open: '/**', lineStart: ' * ', close: ' */' }
},

Expand Down