Using Visual Studio Code as Your Default PowerShell Editor by Tyler Leonhardt

PowerShell Summit videos are recorded on a "best effort" basis. We use a room mic to capture as much room audio as possible, with an emphasis on capturing the speaker. Our recordings are made in a way that minimizes overhead for our speakers and interruptions to our live audience. These recordings are meant to preserve the presentations' information for posterity, and are not intended to be a substitute for attending the Summit in person. These recordings are not intended as professional video training products. We hope you find these videos useful - the equipment used to record these was purchased using generous donations from members of the PowerShell community.

[@strongangel]

Thank You for this, very helpful.

[@mocoroco6028]

It's more hand gymnastics than actually passing good information you can follow.

[@prakashjha26]

Thank you. This was helpful, on my way to using VS Code! Goodbye ISE....

[@Leoninmiami]

Very helpful my friend! Gracias!

[@1464pokemon]

simple, but very useful. thank you for sharing!

[@asmarfontenot]

I like the overlay in your examples that show the key presses you are using. Don't know if a certain screen recording app does that, but it's a nice touch.

[@TheStevenWhiting]

I believe its an extra, small app, I used to use it when recording for Dwarf Fortress but I can't remember what its called. Its free.

[@TheStevenWhiting]

keycast on windows is what its called.

[@sergeyklimenok446]

Hay Tyler Leonhardt 👋

[@_indrid_cold_]

If only we could see variables and their values without having to set breakpoints and debug. I miss Powergui....

[@houstunner44]

YES! That is specifically what brought me to this video which could have really just been a KB.

[@johnmcgiv1]

font too small

[@careyshupe9680]

Sesss