Optimizing Visual Studio Code for Powershell Development

[@andrewhussey2002]

Thanks for this. Might be good to have the URI's in the the video notes.

[@yetanothercuban]

Justin, I often reference this video whenever one of my coworkers wants to get started with Powershell development. Some of the settings you are using are deprecated or no longer available so it would be really great if you could make an updated video with some of the new settings that you might be using

[@boswhizperz]

Looks like the video cuts off early at the end. Is there a second video that picks up where it cut off?

[@sakthipro_YT]

almost an hour length video just to tweak and tune a dev environment? this is a fantastic stuff..

[@TURNERJE12]

Thank you for this! I'm working on a image build for analyst and engineer hosts, and this was the cherry on top.

[@ravilobo7977]

This is an awesome presentation. I learned so many things. Thank you so much.

[@stb74]

How do you change the Name of the terminal to the Powershell version rather than the location.

[@shawngee1]

When I click on the Code.exe after extracting to a folder it gives me a totally black window. Any ideas? I am trying this on Windows 10 Arm installed in Parallels on my M1 Macbook Air.

[@alexk7837]

Great video, Justin. Would be nice to see a few debugging scenarios using VSCode.

[@AyanMullick]

Could one use VSCode as the script pane only and use PS7 running on Windows terminal as the output pane?

[@justingrote4807]

Not directly, but it is possible as a workaround by starting windows terminal powershell and then attaching to that process from VScode. devblogs.microsoft.com/scripting/debugging-powershell-script-in-visual-studio-code-part-2/#powershell-attach-to-host-process

[@AyanMullick]

@@justingrote4807 , thank you for sharing this. I wish there was a way thru 'settings.json' to specify Windows terminal as the default terminal to 'Run Selection' from VSC on PS7 on Windows Terminal without having to get into the debug mode?

[@jgrote]

@@AyanMullick It would be extremely difficult to implement because there's no IPC communication between VSCode and windows terminal. You can feel free to request it or attempt to implement it here! github.com/PowerShell/vscode-powershell/issues

[@AyanMullick]

@@jgrote , you are right. Looks like a 3 year old issue :) github.com/microsoft/vscode/issues/34442

[@wooja2112]

Great video Justin! Are your recommended settings JSON available somewhere for download? Would prefer to copy/paste over trying to retype them :)

[@ocolotap]

Not sure that these are his latest, but I found settings.json here.. github.com/JustinGrote/PWSH24Examples/blob/main/settings.json

[@Our1stPlanet]

Good stuff. I have to get past "There is already a debug config running ..." Help appreciated.

[@frederic_millenial]

1:53 It would have been easier for us you provided the links in the description.

[@jgrote]

Good idea! This is for PWSH24 and I don't have control over the description so @powershell.org may be able to update the comments.

[@cdm297]

Awesome Video Justin, can you please share the link for Cascadia-NF? Many Thanks :-)

[@jackvandeur8849]

There you go www.nerdfonts.com/font-downloads