If you find that your settings.json already has some lines there, make sure you add a , after the last line before entering the text from this lesson or setting changes may not work.
My terminal is refusing to pull up cmd. It only stays on 1.powershell.
Ive tried using other code from other peoples replys about this issue but mine refuses to work.
@Jojo21k let me see if I can help you one step at time, make sure you have Visual Studio 2017 or 2019 installed that is part of your 3rd step below
1st make sure you have c++ extension installed that was given in Sect.1 Ep11
2nd press " once. As you type there should be multiple selections as you type terminal, once you at point of typing shell press down arrow key that has .windows and press enter everything else filled on screen don’t do anything else to that line and press enter
3rd in your windows start button go to search and type developer command prompt right click on it, click properties highlight and copy most everything in target FROM /k all the way to .bat file. you will be posting it like this “terminal.integrated.shellArgs.windows” : [ paste file here add extra \ so that there are two] dont forget to add " for k “/k”, go to file and save and see if it works this is how mine looks. Hope it helps
I really like that time was taken to show where the command line text came from. Because of this, I was able to troubleshoot my own issue. At the time I was going through this video, my install was VS 2019. Just had to change the line slightly!
Hey all, For anyone having trouble with “cl” not working, make sure after you paste the code you save it. It’s easy to forget, but it won’t work otherwise
Most of the issues in this thread are due to people needing to match the ACTUAL locations of their various installs, compilers and cmd instead of copying an example location. So, browse to the locations of the items using your Windows Explorer, etc and note the locations. Edit accordingly, and note the appropriate syntax, such as the double " \ \ " in the directory structure, or the commas at the ends of the lines.
I had to root around in my custom install until I figured out where everything wanted to be found…
\Tools\ Not *\BuildTools* BuildTools directory its for VS2017
if this doesnt works, return to copy the route with \k included. Then add the other symbols. “,” “\” and so on… Try to delete all the line route before. this workds for me.
Note: You do not need the last two lines (the one that has the // in front or the workbench.startupEditor line. Also, the part after C:\\Program^ Files^ ^(x86^)\\Microsoft^ Visual^ Studio\\ may be different than what you have, depending on what version of visual studio code you have. You can figure this out by going to the C drive > Program Files (x86) > Microsoft Visual Studio folder and seeing what folders you have there to see what options there are. If you need help, feel free to reply to me.