The best VsCode setup for Powershell developers

How did we work BEFORE vscode ?

I have been working with Powershell for more then 15 years. As most of the ‘older’ generation, I started using PowerShell ISE, as that was the only option at the time. Coming from VBScript, this was actually SUCH a big improvement, but it had it’s own weaknesses.

In 2017, at the equivalent of the now called PsConfEu (The PowerShell Summit Europe) in 2017 in Amsterdam, we discovered a plugin that would bring PowerShell_ISE to the next level: ‘ISE Steroids’. This was amazing. It solved problems, which I personally didn’t know I had. (Remember, I came from VBScript, so I was basically scripting in Notepad++….).

I liked the plugin so much, I payed for it my self, from my own money, as the company I was working for at the time didn’t see any benefit of using it…

A few years laters, the Powershell team announced they stoped support for POwershell ISE, which ultimataley led to the end of ISE Steroids.

What’s up next ?

Now, I am not saying that I have built something as good as ISE steroids at the time. Far from that actually. BUT, I have been working with VSCode for SO long now, that I have actually really got a sense for WHAT I like, and what I DON’T like.

After changing laptop for the 100th time, and needing to install everything ALL over again, I decided I would try to build something I can re-use EVERYWHERE.

By that, I mean, that I can simply install ALL of my prefered settings, shortcuts, extensions in one GO, and that, on ALL my laptops (Because yes, I actually use a few different ones…).

I have detailed my prefered Extensions, my prefered settings and my prefered shortcuts, in a single youtube video -> [Watch it here]