I recently wrote a post about how to create log files with PowerShell transcription capabilities. What I like about PowerShell transcripts is simplicity. However, as I said in my former post if you want to get the most of it, you should use the Verbose parameter with each cmdlet you launch. Thus, when a warning […]
It’s a known best practice to validate all parameters of a function or a script. But how would you validate a file parameter for a new file?
Displaying firewall rules with PowerShell is very easy with the Get-NetFirewallRule cmdlet.
However, there is a gap: port numbers are not displayed.
In PowerShell 6.2 PSReadLine and your usual shortcuts are not working at all…
Please note that this post is not intended to absolute PowerShell beginners, but rather to Windows PowerShell users who want to give a try to PowerShell Core aka PowerShell 6.x.