Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PowerShell Troubleshooting Guide

You're reading from   PowerShell Troubleshooting Guide Minimize debugging time and maximize troubleshooting efficiency by leveraging the unique features of the PowerShell language

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher
ISBN-13 9781782173571
Length 206 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Michael Shepard Michael Shepard
Author Profile Icon Michael Shepard
Michael Shepard
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. PowerShell Primer FREE CHAPTER 2. PowerShell Peculiarities 3. PowerShell Practices 4. PowerShell Professionalism 5. Proactive PowerShell 6. Preparing the Scripting Environment 7. Reactive Practices – Traditional Debugging 8. PowerShell Code Smells Index

Using –confirm and –whatif


We've already covered what the–confirm and –whatif risk mitigation parameters do. We've also seen how it's not difficult to include support for these parameters in your functions. It is now time to think about how to use them in a troubleshooting session. We will focus on –whatif, but the discussion applies to –confirm in exactly the same way. Obviously, if you are trying to troubleshoot a single function that includes support for –whatif, you can add –whatif to be sure that any system changes that the function would have made are skipped, while finding out what those would have been. This ability is incredibly beneficial to testing because we don't need to worry about the negative effects of running the code.

The way that the risk mitigation parameters (as well as the output preference parameters) work is something like the following. If you specify –whatif in a function call, as the function enters scope, the $whatifpreference variable is set to $true. The $PSCmdlet...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image