xtqqczze
2014ce66c1
Set StrictMode
version 3.0
( #11563 )
2020-02-03 09:44:10 -08:00
xtqqczze
e0d2e2aade
Correct case of $PSHOME special variable
2020-01-13 19:35:33 +00:00
xtqqczze
225164037f
Correct case of $PID special variable
2020-01-13 19:34:38 +00:00
xtqqczze
b5326a8488
Correct case of $Host special variable
2020-01-13 19:34:10 +00:00
xtqqczze
7cb8dc48ea
Correct case of $HOME special variable
2020-01-13 19:33:43 +00:00
xtqqczze
bb58e2aab6
Correct case of $false special variable
2020-01-13 19:25:35 +00:00
xtqqczze
47a3b4e293
Correct case of $true special variable
2020-01-13 19:25:09 +00:00
xtqqczze
4a9d70fdcd
Correct case of $PWD special variable
2020-01-13 19:24:10 +00:00
xtqqczze
42d50434f8
Correct case of $PSCmdlet special variable
2020-01-13 19:19:12 +00:00
xtqqczze
66e0f08ec2
Correct case of $this special variable
2020-01-13 19:18:14 +00:00
xtqqczze
89e33f5772
Correct case of $Matches special variable
2020-01-13 19:15:17 +00:00
xtqqczze
743983390e
Update pester syntax to v4 ( #11544 )
...
* Capitalize 'Should' command and fix whitespace
```powershell
$_ -ireplace '\s?\|\s?should\b',' | Should'
```
* Capitalise and apply hyphen to 'Not' parameter
```powershell
$_ -ireplace '(\| Should) not\b','$1 -Not'
```
* Capitalise and apply hyphen to 'Be' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?) -?be\b','$1 -Be'
```
* Capitalise and apply hyphen to 'BeExactly' parameter
$_ -ireplace '(\| Should(?: -Not)?) -?beexactly\b','$1 -BeExactly'
* Capitalise and apply hyphen to 'BeGreaterThan' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?) -?begreaterthan\b','$1 -BeGreaterThan'
```
* Use 'BeTrue' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?) -Be\s\$?true\b','$1 -BeTrue'
```
* Use 'BeFalse' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?) -Be\s\$?false\b','$1 -BeFalse'
```
* Capitalise and apply hyphen to 'Match' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?)\s-?match\b','$1 -Match'
```
* Capitalise and apply hyphen to 'Throw' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?)\s-?throw\b','$1 -Throw'
```
* Capitalise and apply hyphen to 'BeNullOrEmpty' parameter
```powershell
$_ -ireplace '(\| Should(?: -Not)?)\s-?benullorempty\b','$1 -BeNullOrEmpty'
```
* Capitalise 'Because' parameter
```powershell
$_ -ireplace '\s-because\b',' -Because'
```
* Fix 'BeNullOrEmpty'
2020-01-11 20:41:59 +05:00
xtqqczze
70d9ed4d55
Remove Unicode BOM from text files ( #11546 )
2020-01-11 12:15:34 +05:00
Aditya Patwardhan
2dbb5717ce
Make null member access tests as string to avoid parsing errors ( #11385 )
...
* Make null member access tests as string to avoid parsing errors
* Add PSNullConditionalOperators feature to testmetadata.json
* Add Parsing tests to be skipped
* Add tabcompletion tests
2019-12-21 00:14:07 +00:00
Ilya
54e6199bbb
Use invariant culture string conversion for -replace
operator ( #10954 )
2019-12-19 09:50:46 -08:00
Steve Lee
ed1f6e3144
Make approved features non-experimental ( #11303 )
2019-12-10 15:41:43 -08:00
Aditya Patwardhan
8e76ad00e2
Bump .NET
to 3.1.0
( #11260 )
2019-12-04 13:17:16 -08:00
Aditya Patwardhan
8fcd772353
Bump .NET core framework to 3.1-preview.3
( #11079 )
2019-11-14 17:06:46 -08:00
Ilya
9851b07b1d
Fix style issues ( #10998 )
2019-11-07 11:49:06 -08:00
Aditya Patwardhan
08e120ca2b
Bump .NET core framework to 3.1-preview.2
( #10993 )
2019-11-07 11:45:17 -08:00
Ilya
d58a82ad19
Cleanup: use the built-in type alias ( #10882 )
2019-11-06 08:47:32 +05:00
Aditya Patwardhan
74eaf1980f
Move to .NET Core 3.1 preview 1 ( #10798 )
2019-10-18 16:49:25 -07:00
Robert Holt
2a518fcfe2
Support the pipeline chain operators &&
and ||
in PowerShell language ( #9849 )
2019-10-17 14:43:46 -07:00
Christoph Bergmeister [MVP]
3b93fd285e
Update to .Net Core 3.0 RTM ( #10604 )
2019-09-23 13:10:58 -07:00
Christoph Bergmeister [MVP]
6bf5c7656b
Upgrade .Net Core 3.0 version from Preview 9 to RC1 ( #10552 )
2019-09-16 15:14:21 -07:00
Christoph Bergmeister [MVP]
5a66306c71
Upgrade to Netcoreapp3.0 preview9
( #10484 )
2019-09-06 12:15:49 -07:00
Kirk Munro
cc0fed479a
Add APIs for breakpoint management in runspaces and enable attach to process without BreakAll for PSES ( #10338 )
2019-09-05 11:30:25 -07:00
James Truher [MSFT]
3943f18c28
Alpine validation changes ( #10428 )
2019-08-24 11:35:34 -07:00
Kirk Munro
8b9f4124ce
Add support to ActionPreference.Break
to break into debugger ( #8205 )
2019-08-23 10:34:10 -07:00
Steve Lee
4220271e0e
Move to .NET Core 3.0 preview.8 ( #10351 )
2019-08-15 13:42:17 -07:00
Paul Higinbotham
fbfc57a00c
Implement ForEach-Object -Parallel feature ( #10229 )
2019-08-13 13:40:58 -07:00
Christoph Bergmeister [MVP]
7af38294db
Update PowerShell to build against .NET Core 3.0-preview7 ( #10227 )
2019-08-05 09:56:29 -07:00
Travis Plunk
c64a28eaf1
Merged PR 5767: Fix RegEx DoS issues
...
Fix RegEx DoS issues
2019-07-15 19:52:01 +00:00
Steve Lee
431ef0372a
Fix test password generation rule to meet Windows complexity requirements ( #10143 )
2019-07-12 12:11:45 -07:00
Christoph Bergmeister [MVP]
fe56f9d902
Upgrade .Net Core 3 SDK from preview5 to preview6 and related out of band Nuget packages from 2.1 to 3.0-preview6 ( #9888 )
2019-07-09 14:35:08 -07:00
Kirk Munro
aac4c6ff21
Add module to support Pester tests for automating debugger commands (stepInto, stepOut, etc.), along with basic tests ( #9825 )
2019-06-13 07:19:13 -07:00
Ilya
7e423e7451
Fix minor style issues come from last commits ( #9640 )
2019-06-07 08:35:33 +05:00
Steve Lee
29e21470d9
Port PowerShell to .NET Core 3.0 ( #9597 )
2019-05-21 13:43:51 +08:00
xtqqczze
a702f68974
Ensure Wait-UntilTrue returns $true in Pester tests ( #9458 )
2019-05-01 17:03:43 -07:00
Tyler James Leonhardt
13fd3af810
New New-PSBreakpoint
cmdlet & new -Breakpoint
parameter for Debug-Runspace
( #8923 )
...
This PR does 4 things:
* Adds a new cmdlet `New-PSBreakpoint` which creates new `Breakpoint` objects and writes them to the pipeline
* Adds a `-Breakpoint` parameter to `Debug-Runspace` which will receive `Breakpoint` objects
* Makes the constructors for `*Breakpoint` public for use with the API
* Makes `Debugger.GetBreakpoint(string id)` and `Debugger.GetBreakpoints()` public since `SetBreakpoints` is public
Note: `New-PSBreakpoint` and `Set-PSBreakpoint` (which already exists) are similar... but `Set-PSBreakpoint` also sets the breakpoints in the _current_ runspace. This is not ideal if we want to set breakpoints in a _different runspace than the current one_.
## PR Context
The "Attach to process" debugging experience in the PowerShell extension for VSCode is _ok_ but it's not great.
The reason it's not great is due to the `BreakAll` feature of PowerShell debugging which, when you run `Debug-Runspace`, will break at the first piece of code that gets run. This is not ideal when you "Attach to process" _and then_ run your code in the other runspace.
Today, the experience drops you in `PSReadLine`'s psm1 if PSRL is available or in the vscode PowerShell helper psm1.
It's unexpected for the user and not ideal.
This PR will allow the extension to pass in the breakpoints that need to be set initially with `BreakAll` turned off for none of this silly behavior.
### Silly behavior example
If you want a repro, try this:
PowerShell instance 1:
```
Enter-PSHostProcess -Id $otherprocesspid
Debug-Runspace 1
```
PowerShell instance 2:
```
./runfoo.ps1
```
Note that you end up NOT `runfoo.ps1`
2019-04-13 19:14:53 -07:00
Steve Lee
b8317de469
Update tests to account for when $PSHOME is readonly ( #9279 )
...
Co-Authored-By: SteveL-MSFT <slee@microsoft.com>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
2019-04-04 23:01:01 -07:00
Staffan Gustafsson
e91d6dcf56
Adding CmdletsToExport and AliasesToExport to test module manifests. ( #9108 )
2019-03-18 11:09:05 +05:00
Tyler James Leonhardt
a26d639a47
Fix Enter-PSHostProcess tests flakiness ( #9007 )
2019-03-11 10:41:06 -07:00
dependabot[bot]
98506db714
Build(deps): Bump SelfSignedCertificate in /test/tools/Modules ( #9055 )
2019-03-05 11:32:40 -08:00
Reece Dunham
c14d5dd67f
Remove some of the last AppVeyor references ( #8867 )
...
This removes some of the last mentions of the AppVeyor name. Don't change the title, we don't want the word to appear in the CLs
Also problem: the last references are in the changelogs but I don't want to modify them without committee approval.
## PR Context
it was removed, #8686
2019-02-19 12:44:00 -08:00
Travis Plunk
60ab54d737
Port DotNet fixes from 6.1.3 ( #8914 )
...
Addresses CVE-2019-0657
2019-02-19 10:45:40 -08:00
Travis Plunk
c4b2105a73
Merged PR 6648: Bump SDK and Runtime Versions
...
Bump SDK and Runtime Versions
- Also, fix alpine docker file
- Also, fix extra files being added to some Modules after these changes
2019-01-23 02:18:44 +00:00
Mark Kraus
2dd549e34b
Fix Code Page Parsing Isssue in Invoke-RestMethod ( #8694 )
2019-01-22 10:45:40 -08:00
Travis Plunk
7bf4641444
Fix broken urls ( #8653 )
...
Fix broken URL
- Also, move other static analysis tests into that CI.
- Also, make the link analysis a pester test (partly to make sure the step fails in case of an error)
2019-01-15 16:20:45 -08:00
xtqqczze
6126624b63
Revise use of Start-Sleep cmdlet ( #8633 )
...
* Avoid use of sleep alias (follow-up to #8546 )
* Specify default parameter name
* Shorten overly specific comments
2019-01-15 12:31:52 +05:00