Justin Grote

@slavizh I don't know about "often", I've rarely seen it in the hundreds of customers at my MSP, but it is certainly a consideration. That said, this process will still...

After playing with https://github.com/Azure/bicep/pull/3510 this is what I would see as being ideal: 1. Bicep implements the MSAL azure library same way the Azure Function, etc. extensions do and user...

Did some modifications for my "creative" solution, here it is in action for Policy 

@itfranck while I totally get it, wouldn't it generally be easier to just either: 1. Just have some prior code to convert the custom object into the correct format prior...

To follow up on @SeeminglyScience's work: - Capturing $Error by breaking on erroractionpreference only works reliably on the "throw" keyword, other exceptions don't seem to call it. - The breakpoints...

OK, I've come up with a pretty effective function to break on exceptions in lieu of a proper implementation (https://github.com/PowerShell/PowerShell/issues/2830) https://gist.github.com/JustinGrote/52cf75ea75f2888dbaf4b0c86519d0a6 ## Features 1. Breaks on any terminating exception (doesn't...

There is also a PR to PowerShell 7 to specifically add this functionality to set-breakpoint, so it will be easier to support going forward.

Now that Powershell 7 is out, perhaps it's as "easy" as just wiring up the "Uncaught Exceptions" button to set ErrorActionPreference = 'break' for now?  My current "workaround" is:...

@SeeminglyScience You're right! For some reason I thought it was working on uncaught exceptions only.  Sounds like more of a upstream (Powershell) bug to me, since ErrorActionPreference = 'stop'...

@SydneyhSmith Not sure about the maintain/enforce part because it can always be optional. If a extension author doesn't define the shortcut, you just don't display any help (or display a...