In PowerShell up to 5.1 -Debug set the debug preference to Inquire which allowed the code being run to drop into a nested prompt.
In 6 and 7 it sets it to continue which makes write-debug similar to write-verbose . Inquire has to be set via$debugActionPreference
Further: "Inquire" offers a suspend option (drop to nested prompt) which can't be set via $debugActionPreference and $debugActionPreference offers break (drop to debugger) which can't be selected via the inquire prompt
Are these by design ? If so what's the logic of -debug printing messages but not providing access to debugging ?
In PowerShell up to 5.1
-Debugset the debug preference to Inquire which allowed the code being run to drop into a nested prompt.In 6 and 7 it sets it to continue which makes
write-debugsimilar towrite-verbose. Inquire has to be set via$debugActionPreferenceFurther: "Inquire" offers a suspend option (drop to nested prompt) which can't be set via
$debugActionPreferenceand$debugActionPreferenceoffers break (drop to debugger) which can't be selected via the inquire promptAre these by design ? If so what's the logic of
-debugprinting messages but not providing access to debugging ?