Did your command or script fail and\/or report an error? We hope to have a proper script debugger in a future version, but until then, MSH has some handy features to help you figure out what went wrong. In this series of blog entries, I will present some of those features. Thanks to Jim Truher [MSFT], Bruce Payette [MSFT], and Jeff Jones [MSFT] for their help in putting this together.<\/p>\n
See the Windows “Monad” Shell Beta 2 Documentation Pack (http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=8a3c71d1-18e5-49d7-952a-c55d694ecee3&displaylang=en<\/font><\/a>) for general information about Monad.<\/p>\n Part 1: http:\/\/blogs.msdn.com\/monad\/archive\/2005\/11\/04\/489138.aspx<\/font><\/a> (Terminating vs. Non-Terminating Errors, ErrorRecord) Jon Newman [MSFT]<\/p>\n <\/font><\/font> <\/p>\n <\/p>\n Preferences and Commandline Options (Debug, Verbose etc.)<\/font><\/p>\n <\/b><\/font><\/b>Where set-mshdebug enables script tracing and step-step, Debug and Verbose output allow you to trace and suspend\/restart individual cmdlets. Many cmdlets contain verbose and debug information which they will only print if you explicitly request it; you can also call write-debug, write-verbose, and write-warning (also write-object, write-error and write-progress) in your script.<\/p>\n MSH C:\\temp> $VerbosePreference You can configure the behavior of debug, verbose and errors with both command-line options and preference variables. The following command-line <\/font>options are available on every cmdlet, and can be configured separately for each cmdlet:<\/p>\n Your preference choices are:<\/p>\n You can also set preference variables which set the default behavior where the above command-line options are not specified. The actions which you can configure are:<\/p>\n <\/p>\n <\/b><\/i>Regardless of the ErrorAction settings, $error is always populated (whether you see a message or not):<\/font><\/p>\n MSH C:\\temp> get-process -ErrorAction SilentlyContinue doesnotexist <\/font><\/font><\/font><\/p>\n [Edit: Monad has now been renamed to Windows PowerShell. This script or discussion may require slight adjustments before it applies directly to newer builds.<\/i>]<\/p>\n","protected":false},"excerpt":{"rendered":" Did your command or script fail and\/or report an error? We hope to have a proper script debugger in a future version, but until then, MSH has some handy features to help you figure out what went wrong. In this series of blog entries, I will present some of those features. Thanks to Jim Truher […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10871","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":" Did your command or script fail and\/or report an error? We hope to have a proper script debugger in a future version, but until then, MSH has some handy features to help you figure out what went wrong. In this series of blog entries, I will present some of those features. Thanks to Jim Truher […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10871","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=10871"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10871\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=10871"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=10871"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=10871"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Part 2: http:\/\/blogs.msdn.com\/monad\/archive\/2005\/11\/08\/490130.aspx<\/font><\/a> ($error)
Part 3: http:\/\/blogs.msdn.com\/monad\/archive\/2005\/11\/09\/490625.aspx<\/font><\/a> (write-host)
Part 4: http:\/\/blogs.msdn.com\/monad\/archive\/2005\/11\/09\/491035.aspx<\/font><\/a> (set-mshdebug)<\/p>\n
<\/font>SilentlyContinue
<\/font>MSH C:\\temp> write-verbose test
<\/font>MSH C:\\temp> $VerbosePreference = “Continue”
<\/font>MSH C:\\temp> write-verbose test
<\/font>VERBOSE: test
<\/font>MSH C:\\temp> $VerbosePreference = “Stop”
<\/font>MSH C:\\temp> write-verbose test
<\/font>VERBOSE: test
<\/font>Write-verbose : Command execution stopped because the shell variable “VerbosePreference” is set to Stop.
<\/font>At line:1 char:14
<\/font>+ write-verbose <<<< test
<\/font>MSH C:\\temp> $VerbosePreference = “Inquire”
<\/font>MSH C:\\temp> write-verbose test
<\/font>VERBOSE: test
<\/font>Confirm
<\/font>Continue with this operation?
<\/font>[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): y
<\/font>MSH C:\\temp> <\/font><\/p>\n\n
\n
\n
MSH C:\\temp> $error[0]
get-process : No process with process name ‘doesnotexist’ was found.
At line:1 char:12
+ get-process <<<< -ErrorAction SilentlyContinue doesnotexist
MSH C:\\temp><\/font><\/p>\n