From 8bdda9ffc4f99c682c1e1303b213a7141bf412cb Mon Sep 17 00:00:00 2001 From: David Wilson Date: Thu, 15 Dec 2016 16:49:10 -0800 Subject: [PATCH] Bump version to 0.8.0, update CHANGELOG.md Fixes #382. --- CHANGELOG.md | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++++ package.json | 2 +- src/main.ts | 2 +- 3 files changed, 94 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4741cd4c42..e20c254952 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,97 @@ # vscode-powershell Release History +## 0.8.0 +### Friday, December 16, 2016 + +#### Improved PowerShell session management + +It's now much easier to manage the active PowerShell session. We've added a +new item to the status bar to indicate the state of the session and the version +of PowerShell you're using: + +![Screenshot of status indicator](https://cloud.githubusercontent.com/assets/79405/21247551/fcf2777c-c2e4-11e6-9659-7349c35adbcd.png) + +When this status item is clicked, a new menu appears to give you some session +management options: + +![Screenshot of session menu](https://cloud.githubusercontent.com/assets/79405/21247555/009fa64c-c2e5-11e6-8171-76914d3366a0.png) + +You can restart the active session, switch between 32-bit and 64-bit PowerShell on +Windows or switch to another PowerShell process (like a 6.0 alpha build) that +you've configured with the `powershell.developer.powerShellExePath`. + +We've also improved the overall experience of loading and using the extension: + +- It will prompt to restart the PowerShell session if it crashes for any reason +- It will also prompt to restart the session if you change any relevant PowerShell + configuration setting like the aforementioned `powershell.developer.powerShellExePath`. +- You can easily access the logs of the current session by running the command + `Open PowerShell Extension Logs Folder`. + +#### Create new modules with Plaster + +In this release we've added integration with the [Plaster](https://github.com/PowerShell/Plaster) +module to provide a `Create New Project from Plaster Template` command. This command will +walk you through the experience of selecting a template and filling in all of +the project details: + +![Screenshot of Plaster template selection](https://cloud.githubusercontent.com/assets/79405/21247560/087b47a4-c2e5-11e6-86e7-ba3727b5e36d.png) + +![Screenshot of Plaster input](https://cloud.githubusercontent.com/assets/79405/21247562/0a79b130-c2e5-11e6-97e9-cfd672803f75.png) + +We include one basic project template by default and will add more in the very +near future. However, you won't need to update the PowerShell extension to get these +new templates, they will appear when you install an update to the Plaster module from +the [PowerShell Gallery](https://www.powershellgallery.com/). + +Check out [Plaster's documentation](https://github.com/PowerShell/Plaster/tree/master/docs/en-US) +for more details on how it can be used and how you can create your own templates. + +#### New "quick fix" actions for PSScriptAnalyzer rules + +The PowerShell extension now uses any "suggested corrections" which are returned with +a rule violation in your script file to provide a "quick fix" option for the affected +section of code. For example, when the `PSAvoidUsingCmdletAliases` rule finds the use +of a non-whitelisted alias, you will see a light bulb icon that gives the option to +change to the full name (right click or Ctrl+. on the marker): + +![Screenshot of PSScriptAnalyzer quick fix](https://cloud.githubusercontent.com/assets/79405/21247558/05887e86-c2e5-11e6-9c67-e4558a7e2dba.png) + +If you'd like to see more quick fixes for PowerShell code, head over to the +[PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) GitHub page and +get involved! + +#### Easily enable and disable PSScriptAnalyzer rules + +Another improvement related to PSScriptAnalyzer is the ability to change the active +PSScriptAnalyzer rules in the current editing session using a helpful selection menu: + +![Screenshot of PSScriptAnalyzer rule selection](https://cloud.githubusercontent.com/assets/79405/21247557/037888b6-c2e5-11e6-816f-6732e13cddb7.png) + +You can enable and disable active rules by running the `Select PSScriptAnalyzer Rules` +command. For now this only changes the active session but in a future release we will +modify your PSScriptAnalyzer settings file so that the changes are persisted to future +editing sessions. + +#### New "hit count" breakpoints in the debugger + +When debugging PowerShell scripts you can now set "hit count" breakpoints which +cause the debugger to stop only after the breakpoint has been encountered a specified +number of times. + +![Screenshot of a hit count breakpoint](https://cloud.githubusercontent.com/assets/79405/21247563/0c159202-c2e5-11e6-8c91-36791c4fa804.png) + +#### Other fixes and improvements + +- We now provide snippets for the `launch.json` configuration file which make it easier + to add new PowerShell debugging configurations for your project. +- In PowerShell `launch.json` configurations, the `program` parameter has now been + renamed to `script`. Configurations still using `program` will continue to work. +- Fixed #353: Cannot start PowerShell debugger on Windows when offline +- Fixed #217: PowerShell output window should be shown when F8 is pressed +- Fixed #292: Check for Homebrew's OpenSSL libraries correctly on macOS +- Fixed #384: PowerShell snippets broken in VS Code 1.8.0 + ## 0.7.2 ### Friday, September 2, 2016 diff --git a/package.json b/package.json index ae4b16ae73..a0f58698e7 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "PowerShell", "displayName": "PowerShell", - "version": "0.7.2", + "version": "0.8.0", "publisher": "ms-vscode", "description": "Develop PowerShell scripts in Visual Studio Code!", "engines": { diff --git a/src/main.ts b/src/main.ts index 644b691018..a08ffa2fd3 100644 --- a/src/main.ts +++ b/src/main.ts @@ -21,7 +21,7 @@ import { CodeActionsFeature } from './features/CodeActions'; // NOTE: We will need to find a better way to deal with the required // PS Editor Services version... -var requiredEditorServicesVersion = "0.7.2"; +var requiredEditorServicesVersion = "0.8.0"; var logger: Logger = undefined; var sessionManager: SessionManager = undefined;