The story of installing PowerShell7

powershell7 コンピュータ
I installed PowerShell7 on my Windows 10 PC.

Install to

Since the shortcut “PowerShell 7” was created in the start menu, check the location and name of the executable file in the properties.

"C:Program FilesPowerShell7pwsh.exe" -WorkingDirectory ~

The file name of the executable file is pwsh.exe. Version 5.1 of PowerShell was a PowerShell .exe, so there seems to be no inconvenience in calling both.

Launch PowerShell7

Press the “Win” key and type “pwsh” to start it with the enter key. Similarly, when you type “powershell” and press the enter key, PowerShell 5.1 was confirmed.

Output and encoding of text files

echo "日本語" | Out-File sample.txt

When I opened it with Notepad, I was able to confirm that the encoding was UTF8 and there was no BOM.

Check the cmdlet alias that is being set

Name    Definition
?       Where-Object
%       ForEach-Object
ac      Add-Content
cat     Get-Content
cd      Set-Location
chdir   Set-Location
clc     Clear-Content
clear   Clear-Host
clhy    Clear-History
cli     Clear-Item
clp     Clear-ItemProperty
cls     Clear-Host
clv     Clear-Variable
cnsn    Connect-PSSession
compare Compare-Object
copy    Copy-Item
cp      Copy-Item
cpi     Copy-Item
cpp     Copy-ItemProperty
cvpa    Convert-Path
dbp     Disable-PSBreakpoint
del     Remove-Item
diff    Compare-Object
dir     Get-ChildItem
dnsn    Disconnect-PSSession
ebp     Enable-PSBreakpoint
echo    Write-Output
epal    Export-Alias
epcsv   Export-Csv
erase   Remove-Item
etsn    Enter-PSSession
exsn    Exit-PSSession
fc      Format-Custom
fhx     Format-Hex
fl      Format-List
foreach ForEach-Object
ft      Format-Table
fw      Format-Wide
gal     Get-Alias
gbp     Get-PSBreakpoint
gc      Get-Content
gcb     Get-Clipboard
gci     Get-ChildItem
gcm     Get-Command
gcs     Get-PSCallStack
gdr     Get-PSDrive
gerr    Get-Error
ghy     Get-History
gi      Get-Item
gin     Get-ComputerInfo
gjb     Get-Job
gl      Get-Location
gm      Get-Member
gmo     Get-Module
gp      Get-ItemProperty
gps     Get-Process
gpv     Get-ItemPropertyValue
group   Group-Object
gsn     Get-PSSession
gsv     Get-Service
gtz     Get-TimeZone
gu      Get-Unique
gv      Get-Variable
h       Get-History
history Get-History
icm     Invoke-Command
iex     Invoke-Expression
ihy     Invoke-History
ii      Invoke-Item
ipal    Import-Alias
ipcsv   Import-Csv
ipmo    Import-Module
irm     Invoke-RestMethod
iwr     Invoke-WebRequest
kill    Stop-Process
ls      Get-ChildItem
man     help
md      mkdir
measure Measure-Object
mi      Move-Item
mount   New-PSDrive
move    Move-Item
mp      Move-ItemProperty
mv      Move-Item
nal     New-Alias
ndr     New-PSDrive
ni      New-Item
nmo     New-Module
nsn     New-PSSession
nv      New-Variable
ogv     Out-GridView
oh      Out-Host
popd    Pop-Location
ps      Get-Process
pushd   Push-Location
pwd     Get-Location
r       Invoke-History
rbp     Remove-PSBreakpoint
rcjb    Receive-Job
rcsn    Receive-PSSession
rd      Remove-Item
rdr     Remove-PSDrive
ren     Rename-Item
ri      Remove-Item
rjb     Remove-Job
rm      Remove-Item
rmdir   Remove-Item
rmo     Remove-Module
rni     Rename-Item
rnp     Rename-ItemProperty
rp      Remove-ItemProperty
rsn     Remove-PSSession
rv      Remove-Variable
rvpa    Resolve-Path
sajb    Start-Job
sal     Set-Alias
saps    Start-Process
sasv    Start-Service
sbp     Set-PSBreakpoint
scb     Set-Clipboard
select  Select-Object
set     Set-Variable
shcm    Show-Command
si      Set-Item
sl      Set-Location
sleep   Start-Sleep
sls     Select-String
sort    Sort-Object
sp      Set-ItemProperty
spjb    Stop-Job
spps    Stop-Process
spsv    Stop-Service
start   Start-Process
stz     Set-TimeZone
sv      Set-Variable
tee     Tee-Object
type    Get-Content
where   Where-Object
wjb     Wait-Job
write   Write-Output

$profile location



I only touched it a little, but it seems that the basic operation can be handled by knowledge of PowerShell 5.1.

The object returned by Invoke-WebRequest did not have a ParsedHtml property. I think that it can not be helped, because it seems to be derived from IE, but it is a pity because I expected it to be supported in PowerShell 7. (Do you want to study RPA?)