Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn PowerShell Core 6.0

You're reading from   Learn PowerShell Core 6.0 Automate and control administrative tasks using DevOps principles

Arrow left icon
Product type Paperback
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Length 552 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Authors (2):
Arrow left icon
David das Neves David das Neves
Author Profile Icon David das Neves
David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Author Profile Icon Jan-Hendrik Peters
Jan-Hendrik Peters
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Current PowerShell Versions FREE CHAPTER 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 18. PowerShell ISE Hotkeys 19. Assessments 20. Other Books You May Enjoy

ConvertTo-Breakpoint

Among the huge number of useful modules on the internet, there is ConvertTo-Breakpoint by Kevin Marquette. The module is available on PowerShell Gallery and is being developed on GitHub at https://github.com/KevinMarquette/ConvertTo-Breakpoint. This module allows you to simply create breakpoints from error records, which has been a huge time-saver for us in the past.

Errors in PowerShell contains a lot of additional info, such as the target object, the category, and also the script stack trace. Kevin made use of that property to parse where in the script an issue occurred, to automatically set one or more new breakpoints. It is even possible to set breakpoints for all errors present in the stack trace. Take a look at the following code:

# Get the module
if (-not (Get-Module ConvertTo-Breakpoint -List))
{
Install-Module ConvertTo-Breakpoint -Scope CurrentUser...
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