{"id":1051,"date":"2014-07-05T00:01:00","date_gmt":"2014-07-05T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2014\/07\/05\/weekend-scripter-using-try-catch-finally-blocks-for-powershell-error-handling\/"},"modified":"2014-07-05T00:01:00","modified_gmt":"2014-07-05T00:01:00","slug":"weekend-scripter-using-try-catch-finally-blocks-for-powershell-error-handling","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/weekend-scripter-using-try-catch-finally-blocks-for-powershell-error-handling\/","title":{"rendered":"Weekend Scripter: Using Try, Catch, Finally Blocks for PowerShell Error Handling"},"content":{"rendered":"

Summary<\/b>: Microsoft PFE, Ashley McGlone, talks about using Try, Catch, Finally blocks for error handling in Windows PowerShell.\nMicrosoft Scripting Guy, Ed Wilson, is here. Today’s guest blogger is Ashley McGlone, a Microsoft premier field engineer. Ashley is a popular speaker at our Windows PowerShell Saturday events. He regularly blogs about Active Directory and Windows PowerShell at Goatee PFE<\/a>. You can follow him on Twitter as @GoateePFE. Take it away, Ashley…\nWhy do scripts have errors? That is a long philosophical debate, and there is more than one correct answer. The generally accepted answer is that they are written by humans, and humans are not perfect. Even when considering all of the reasons there are errors in scripts, the root cause is usually a difference in expectations. I expect the code or data to be X, but really it is Y. And that is why we need error handling.\nThere are many ways to handle errors in Windows PowerShell, including:<\/p>\n