Menu
Imagine if you have a script containing a single line of code like
ni -type file foobar.txt
where the -verbose flag is not supplied to the ni command. Is there a way to set the Verbosity at a global PSSession level if I were to run this script to force verbosity? The reason I ask is that I have a group of about 60 scripts which are interdependent and none of these supply -verbose to any commands they issue and I'd like to see the entire output when I call the main entry point powershell script.
903
By default, the verbose message stream is not displayed, but you can display it by changing the value of the $VerbosePreference variable or using the Verbose common parameter in any command. Also, Write-Verbose writes to the verbose output stream and you can capture it separately.
The Verbose parameter overrides the value of the $VerbosePreference variable for the current command. Because the default value of the $VerbosePreference variable is SilentlyContinue, verbose messages aren't displayed by default. -Verbose:$true has the same effect as -Verbose.
ErrorActionPreference variable in PowerShell is to control the non-terminating errors by converting them to terminating errors. Error handling depends upon which value you assign to $ErrorActionPreference variable.
You could also do:
$global:VerbosePreference = 'continue'
Works better then PSDefaultParameters as it tolerates function not having Verbose param.
75
Use $PSDefaultParameterValues:
$PSDefaultParameterValues['New-Item:Verbose'] = $true
Set that in the Global scope, and then the default value of -Verbose for the New-Item cmdlet will be $True.
You can use wildcards for the cmdletsyou want to affect:
$PSDefaultParameterValues['New-*:Verbose'] = $true
Will set it for all New-* cmdlets.
$PSDefaultParameterValues['*:Verbose'] = $true
will set it for all cmdlets.
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
