# Do I need to configure anything in VSCode to switch to using v1.6.0?

**URL:** <https://discourse.julialang.org/t/do-i-need-to-configure-anything-in-vscode-to-switch-to-using-v1-6-0/58122>\
**Category:** VS Code\
**Tags:** vscode, versions, configuration\
**Created:** [March 28, 2021, 4:39pm UTC](https://discourse.julialang.org/t/do-i-need-to-configure-anything-in-vscode-to-switch-to-using-v1-6-0/58122 "2021-03-28T16:39:39Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![affans](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/affans/32/11911_2.png) [@affans](https://discourse.julialang.org/u/affans)\
**Post date:** [March 28, 2021, 11:08pm UTC](https://discourse.julialang.org/t/do-i-need-to-configure-anything-in-vscode-to-switch-to-using-v1-6-0/58122/19 "2021-03-28T23:08:04Z")

</div>

I personally think putting it in PATH is a better option rather than fixing it in vscode. This is because I work in tandem with vscode, vscode internal terminal, and a REPL running on an external terminal. It would suck to have vscode launch 1.6 (since the path is explicility specified) and version 1.x run when typing in `julia` in the terminal.

To answer your question directly, if you google “Environment Variable Windows”, you will get very explicit instructions. (For example: [Setting global environment variables on Windows – Shotgun Support (shotgunsoftware.com)](https://support.shotgunsoftware.com/hc/en-us/articles/114094235653-Setting-global-environment-variables-on-Windows#:~:text=Windows%207,to%20edit%2C%20and%20click%20Edit.). I would advise you to play around here and see what is inside the variable `PATH`.

---

_[View the full topic](https://discourse.julialang.org/t/do-i-need-to-configure-anything-in-vscode-to-switch-to-using-v1-6-0/58122)._
