Sam Erde
@samerde.day3bits.com
Microsoft PowerShell MVP that is passionate about helping others succeed with Active Directory, Entra ID, Defender XDR, and Microsoft 365. Always learning! ✝️👨👩👧👦☕
GitHub.com/SamErde
Blog: day3bits.com
GitHub.com/SamErde
Blog: day3bits.com
Those recommendations make perfect sense. I'll pass that along, with thanks!
November 12, 2025 at 6:31 PM
Those recommendations make perfect sense. I'll pass that along, with thanks!
Glad I could help! :)
November 10, 2025 at 5:01 PM
Glad I could help! :)
Did I just do half of your homework? 😂
November 10, 2025 at 4:59 PM
Did I just do half of your homework? 😂
I'm sure it would help because of how the detailed view includes the full stack trace, so the agent would have explicit information instead of having to infer what the exact process was leading up to the error.
November 10, 2025 at 4:59 PM
I'm sure it would help because of how the detailed view includes the full stack trace, so the agent would have explicit information instead of having to infer what the exact process was leading up to the error.
This is a great example for a demo that I'm giving later this week!
@(1..5) | ForEach-Object { New-Item -Name "Day$_" -ItemType Directory }
@(1..5) | ForEach-Object { New-Item -Name "Day$_" -ItemType Directory }
November 10, 2025 at 4:56 PM
This is a great example for a demo that I'm giving later this week!
@(1..5) | ForEach-Object { New-Item -Name "Day$_" -ItemType Directory }
@(1..5) | ForEach-Object { New-Item -Name "Day$_" -ItemType Directory }
Interesting thought! I can imagine that might help when Copilot runs the script to test its output or when I copy/paste the output for the agent to review for me.
November 10, 2025 at 4:54 PM
Interesting thought! I can imagine that might help when Copilot runs the script to test its output or when I copy/paste the output for the agent to review for me.
Oh, to be honest, I wasn't aware of the command to restart the extension host! Going to add that to my bag of tricks. (I did try restarting the PowerShell session and VS Code itself.)
November 6, 2025 at 12:10 PM
Oh, to be honest, I wasn't aware of the command to restart the extension host! Going to add that to my bag of tricks. (I did try restarting the PowerShell session and VS Code itself.)
100% -- I did try these, and it sometimes feels too frequently necessary. Nice idea on the key binding!
November 6, 2025 at 12:09 PM
100% -- I did try these, and it sometimes feels too frequently necessary. Nice idea on the key binding!
Tried all of the above. It was the obvious answer: an extension.
November 6, 2025 at 12:08 PM
Tried all of the above. It was the obvious answer: an extension.
Haha, yes, or with only one!
November 6, 2025 at 12:08 PM
Haha, yes, or with only one!
Ah. That was either just before my time or during the time that my family had no TV! 😄
November 6, 2025 at 12:07 PM
Ah. That was either just before my time or during the time that my family had no TV! 😄
I like to keep it pretty simple. Here's my Comply theme for Oh My Posh:
github.com/SamErde/Powe...
github.com/SamErde/Powe...
October 28, 2025 at 2:00 PM
I like to keep it pretty simple. Here's my Comply theme for Oh My Posh:
github.com/SamErde/Powe...
github.com/SamErde/Powe...
PowerShell's standard naming convention for cmdlets and functions is {Verb}-{Noun}. 😉☕
October 28, 2025 at 1:56 PM
PowerShell's standard naming convention for cmdlets and functions is {Verb}-{Noun}. 😉☕
LOL, I'm not sure what that is 😆 but I love the coffee name because all standard PowerShell function and cmdlet names begin with a verb!
October 28, 2025 at 1:55 PM
LOL, I'm not sure what that is 😆 but I love the coffee name because all standard PowerShell function and cmdlet names begin with a verb!
Oh, you know it absolutely does! 🛎️☕
October 24, 2025 at 4:25 PM
Oh, you know it absolutely does! 🛎️☕