Skip to content

Commit d897763

Browse files
daviwildaviwil
committed
Bump version to 0.10.0, update CHANGELOG.md
1 parent 3f92dd0 commit d897763

File tree

3 files changed

+129
-2
lines changed

3 files changed

+129
-2
lines changed

‎CHANGELOG.md

+127
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,132 @@
11
# vscode-powershell Release History
22

3+
## 0.10.0
4+
### Tuesday, March 14, 2017
5+
6+
#### New interactive console experience
7+
8+
We are excited to provide you with the first release of our new interactive
9+
console experience! When you open up a PowerShell script file, you will
10+
be greeted with a new VS Code integrated terminal window called
11+
"PowerShell Integrated Console"
12+
13+
[TODO SCREENSHOT]
14+
15+
In this console you will have an experience that falls somewhere between
16+
the PowerShell ISE and the PowerShell console host:
17+
18+
- Tab completion for commands and their parameters
19+
- Basic command history can be accessed using the up/down arrow keys
20+
- The `psedit` command opens existing files in an editor pane
21+
- Pressing <kbd>F8</kbd> in an editor pane runs the current line or selection in the console
22+
- Script debugging shares the same console session with the editor for
23+
a true ISE-like debugging experience
24+
- Native applications like `git` are fully supported
25+
26+
It even works with your fancy prompt function if configured in in your
27+
VS Code profile (`$HOME\Documents\WindowsPowerShell\Microsoft.VSCode_profile.ps1`):
28+
29+
[TODO SCREENSHOT]
30+
31+
The integrated console is supported on PowerShell v3 through v6 and works
32+
on Linux and macOS with PowerShell Core. By default you don't have to
33+
configure which PowerShell to run, we will pick an appropriate default
34+
based on your platform. If you'd like to choose a different install
35+
of PowerShell you can always change the `powershell.developer.powerShellExePath`
36+
setting.
37+
38+
Keep in mind that this is the first release for this feature and there are
39+
bound to be issues and missing functionality. Please feel free to file
40+
issues for any bugs or feature requests you have!
41+
42+
##### Known Issues and Limitations
43+
44+
- [#535](https://github.com/PowerShell/vscode-powershell/issues/535) PSReadline
45+
is currently **not** supported in the integrated console. We will enable this
46+
in a future release.
47+
- [#534](https://github.com/PowerShell/vscode-powershell/issues/534) Integrated console
48+
prompt is not restarted when you stop the debugging of a local runspace in another
49+
process. This will be addressed soon in a patch update.
50+
- [#533](https://github.com/PowerShell/vscode-powershell/issues/533) Backspace key
51+
does not work in the integrated console on Linux and macOS. The workaround for now
52+
is to use <kbd>Ctrl+H</kbd> instead of the Backspace key. This will be addressed
53+
soon in a patch update.
54+
- [#536](https://github.com/PowerShell/vscode-powershell/issues/536) Integrated console
55+
sometimes does not have a scrollbar at startup. The workaround is to resize the width
56+
of the VS Code window slightly and the scrollbar will appear. This will be addressed
57+
soon in a patch update.
58+
59+
#### Get-Credential and PSCredential support
60+
61+
Now that we have the integrated console, we have added support for the `Get-Credential`
62+
cmdlet, `Read-Host -AsSecureString`, and any input prompt of type `SecureString` or `PSCredential`. When you run any of these cmdlets you will be prompted inside of
63+
the integrated console:
64+
65+
[TODO SCREENSHOT]
66+
67+
#### Code formatting improvements
68+
69+
We now support VS Code's `editor.formatOnType` setting so that your code gets formatted
70+
as you type! Formatting will be triggered when you press Enter or the closing curly
71+
brace character `}`.
72+
73+
Based on your feedback, we've also added new code formatting options, all of which
74+
are turned on by default:
75+
76+
- `powershell.codeFormatting.newLineAfterCloseBrace` - Causes a newline to be inserted
77+
after a closing brace in multi-line expressions like if/else
78+
- `powershell.codeFormatting.whitespaceBeforeOpenBrace` - Causes whitespace to be
79+
inserted before an open brace like `Foreach-Object {`
80+
- `powershell.codeFormatting.whitespaceBeforeOpenParen` - Causes whitespace to be
81+
inserted before an open parentheses like `if (`
82+
- `powershell.codeFormatting.whitespaceAroundOperator` - Causes whitespace to be
83+
inserted around operators like `=` or `+`
84+
- `powershell.codeFormatting.whitespaceAfterSeparator` - Causes whitespace to be
85+
inserted around separator characters like `;` and `,`
86+
- `powershell.codeFormatting.ignoreOneLineBlock` - Single-line expressions, like
87+
small if/else statements, will not be expanded to multiple lines.
88+
89+
We've also made many improvements to the performance and stability of the formatter.
90+
91+
#### Debugging improvements
92+
93+
We've added a new configuration for debugging your Pester tests. By default it
94+
merely runs `Invoke-Pester` at the workspace path, but you can also edit the
95+
configuation to add additional arguments to be passed through.
96+
97+
We've also added support for column breakpoints. Now you can set a breakpoint
98+
directly within a pipeline by placing your cursor at any column on a line and
99+
running the `Debug: Column Breakpoint` command:
100+
101+
[TODO SCREENSHOT]
102+
103+
For the latest PowerShell Core release (alpha.17), we have also added the ability
104+
to step into ScriptBlocks that are executed on another machine using `Invoke-Command
105+
-Computer`.
106+
107+
[TODO SCREENSHOT]
108+
109+
If you set a breakpoint on an `Invoke-Command` line and then press `F11`
110+
you will be able to step through the ScriptBlock as it runs in the remote machine:
111+
112+
[TODO SCREENSHOT]
113+
114+
Note that you cannot currently set breakpoints in the script listing file as
115+
this code is being executed without an actual script file on the remote machine.
116+
117+
#### Other fixes and improvements
118+
119+
- [#427](https://github.com/PowerShell/vscode-powershell/issues/427) -
120+
The keybinding for "Expand Alias" command has been changed to <kbd>Shift+Alt+E</kbd>
121+
- [#519](https://github.com/PowerShell/vscode-powershell/issues/519) -
122+
Debugger hangs after continuing when watch expressions are set
123+
- [#448](https://github.com/PowerShell/vscode-powershell/issues/448) -
124+
Code formatter should keep indentation for multi-line pipelines
125+
- [#518](https://github.com/PowerShell/vscode-powershell/issues/518) -
126+
Code formatter fails when dollar-paren `$()` expressions are used
127+
- [#447](https://github.com/PowerShell/vscode-powershell/issues/447) -
128+
Code formatter crashes when run on untitled documents
129+
3130
## 0.9.0
4131
### Thursday, January 19, 2017
5132

‎package.json

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

‎src/main.ts

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ import { DocumentFormatterFeature } from './features/DocumentFormatter';
2727

2828
// NOTE: We will need to find a better way to deal with the required
2929
// PS Editor Services version...
30-
var requiredEditorServicesVersion = "0.9.0";
30+
var requiredEditorServicesVersion = "0.10.0";
3131

3232
var logger: Logger = undefined;
3333
var sessionManager: SessionManager = undefined;

0 commit comments

Comments
 (0)