less than 1 minute read

Developing PowerShell scripts and modules that reference classes and binary modules can be a bit painful, as in order to load a new version of the class or module you need to restart the PowerShell session to unload the old version. Having to manually restart PowerShell every time you make a change to a class or binary module gets old pretty fast. Luckily, the Visual Studio Code PowerShell extension has a feature that can help with this.

Once you’ve installed the PowerShell extension in VS Code, you can enable the PowerShell › Debugging: Create Temporary Integrated Console setting.

Screenshot of the Visual Studio Code setting to enable PowerShell temporary integrated console

Now every time you debug a PowerShell script, it will first create a new temporary PowerShell terminal and then run the script in that terminal, ensuring no previous variables are still lingering in memory and that the latest version of your classes and binary modules are loaded. No more manually restarting your PowerShell terminals when developing classes or binary modules!

I hope you find this useful. For more Visual Studio Code settings you might want to tweak, check out this post.

Happy coding!


Leave a Comment

Your email address will not be published. Required fields are marked *