The Invoke-BatchFile command executes the specified batch file with, then calls set to dump the new environment table to file for parsing. I initially thought something might have happened to the Invoke-BatchFile implementation in PSCX, prompting me to voice an issue to that team 2. Upon upgrading to the 16.2.1 release, my profile began coughing up an error: "The input line is too long. This command required maintenance over time since the path was specific to the installed edition and major version of Visual Studio. I would use the Invoke-BatchFile cmdlet in my profile to execute the VsDevCmd.bat file in the Common7Tools folder of the current Visual Studio installation. Until the 16.2.1 release 1 of Visual Studio 2019, I used the inimitable PowerShell Community Extensions (PSCX) module to execute batch files to alter the current environment variables (PATH, etc.). Even though I’ve been using Ubuntu as my main platform for development and have consequently gotten into ZSH and BASH scripting, I still use PowerShell daily, but now with a new cmdlet: Enter-VsDevShell.
So one of the first things I do when provisioning a new developer machine is grab a copy of my PowerShell profile from my GitHub repository. A New Way to Add Visual Studio Tools to Your PowerShell Environment With Enter-VsDevShell PowerShell All the Thingsįor many years I’ve enjoyed using a PowerShell console as my go-to CLI for interacting with.
0 kommentar(er)
