Skip to content

Prepare 0.6.0 release #172

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.

Sign up for GitHub

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 1 commit into from
May 12, 2016
Merged

Prepare 0.6.0 release #172

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
48 changes: 48 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,53 @@
# vscode-powershell Release History

## 0.6.0
### Thursday, May 12, 2016

#### 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](https://powershell.github.io/PowerShellEditorServices/guide/extensions.html)
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`
- In Visual Studio Code the profile name is `Microsoft.VSCode_profile.ps1`.
- `$host.Name` now returns "Visual Studio Code Host" and `$host.Version` returns
the version of the PowerShell extension that is being used.

#### Other improvements

- IntelliSense for static methods and properties now works correctly. If you
type `::` after a type such as `[System.Guid]` you will now get the correct
completion results. This also works if you press `Ctrl+Space` after the `::`
characters.
- `$env` variables now have IntelliSense complete correctly.
- Added support for new VSCode command `Debug: Start Without Debugging`. Shortcut
for this command is <kbd>Ctrl+F5</kbd>.
- Changed the keyboard shortcut for `PowerShell: Expand Alias` from <kbd>Ctrl+F5</kbd> to <kbd>Ctrl+Alt+e</kbd>.
- Added support for specifying a PSScriptAnalyzer settings file by
providing a full path in your User Settings for the key `powershell.scriptAnalysis.settingsPath`.
You can also configure the same setting in your project's `.vscode\settings.json`
file to contain a workspace-relative path. If present, this workspace-level setting
overrides the one in your User Settings file. See the extension's `examples\.vscode\settings.json`
file for an example.
- The debug adapter now does not crash when you attempt to add breakpoints
for files that have been moved or don't exist.
- Fixed an issue preventing output from being written in the debugger if you
don't set a breakpoint before running a script.

#### New configuration settings

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

## 0.5.0
Copy link
Contributor

@rkeithhill rkeithhill May 12, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Added support for new VSCode command Debug: Start Without Debugging. Shortcut for this command is Ctrl+F5.
  • Changed the keyboard shortcut for PowerShell: Expand Alias from Ctrl+F5 to Ctrl+Alt+e.
  • Added support for specifying either a user PSScriptAnalyzer settings file by setting a full path in your User Settings file for the setting powershell.scriptAnalysis.settingsPath. You can also configure this setting in your workspace's .vscode\settings.json file to a workspace relative path. This settings file overrides the one configured in your User Settings file - if it's configured there. See the extension's Examples\.vscode\settings.json file for an example.

### Thursday, March 10, 2016

Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "PowerShell",
"displayName": "PowerShell",
"version": "0.5.0",
"version": "0.6.0",
"publisher": "ms-vscode",
"description": "Develop PowerShell scripts in Visual Studio Code!",
"engines": {
Expand Down