profile for Gajendra D Ambi on Stack Exchange, a network of free, community-driven Q&A sites

Saturday, January 27, 2018

My Visual Studio Code Settings

So this is my visual studio code setting. Just a note for me in the future to look back in case I lose it.
ctrl+, and copy paste this.
How to setup powershell 6 core on visual studio code?
https://docs.microsoft.com/en-us/powershell/scripting/core-powershell/vscode/using-vscode?view=powershell-6


{
"files.defaultLanguage": "powershell",
"powershell.powerShellExePath": "C:\\Program Files\\PowerShell\\6.0.0\\pwsh.exe",
"editor.mouseWheelZoom": true,
"terminal.integrated.shell.windows": "C:\\Program Files\\PowerShell\\6.0.0\\pwsh.exe",
"editor.renderWhitespace": "all",
"editor.renderControlCharacters": true,
"files.trimTrailingWhitespace": true,
"workbench.iconTheme": "material-icon-theme",
"workbench.colorTheme": "Atom One Dark",
"terminal.integrated.fontSize": 22,
}

update:
I am pretty sure you might later end up using some terminal plugin inside later and that will most probably be powershell.
Make sure you configure your powershell exactly the way below to be worry free about the crappy microsoft error about non digitally signed scripts. Untill I did this exact thing I was never able to activate virtual environments for python because ps scripts were blocked.

  • Close all command line windows,consoles, terminals or any other IDE which has it open via a plugin or extention ex: atom with terminal plus plugin.
  • Set your execution policy such that it is applied for the whole damn local machine and not just administrator or any one particular user.
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope LocalMachine