# VS Code extension v0.7 released

**URL:** <https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284>\
**Category:** Community\
**Tags:** announcement\
**Created:** [August 8, 2017, 5:20pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284 "2017-08-08T17:20:56Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [August 8, 2017, 5:20pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/1 "2017-08-08T17:20:56Z")

</div>

We released v0.7.0 of the julia VS Code extension to the marketplace.

This new version has massive amount of improvements and bug fixes to the IntelliSense features, mostly thanks to @ZacLN, and some other new features:

- In general the IntelliSense features should work with many more corner cases, be more robust etc. We fixed many, many bugs during the release candidate phase thanks to some fantastic bug reports, so I’m pretty optimistic that this should be the most stable version we have released so far.
- We use the VS Code task system for running builds, tests and benchmarks now. If you open a folder, the extension will automatically detect whether that folder has a build, test or benchmark script. If it does, it will add detected tasks to the default list of tasks in VS Code, and you can run those tasks via the VS Code task runner.
- We now support the rename refactoring in the editor.
- We added a reload modules command.

If you do find bugs, please report them at [GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code](https://github.com/JuliaEditorSupport/julia-vscode). If things work just fine, we don’t mind feedback either, always helps with the motivation 🙂

Best,  
David & Zac

---

<div class="post-metadata">

**Author:** ![anon94023334](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@anon94023334](https://discourse.julialang.org/u/anon94023334)\
**Post date:** [August 8, 2017, 6:10pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/2 "2017-08-08T18:10:33Z")

</div>

Thank you for all your work on this extension. It’s really useful.

---

<div class="post-metadata">

**Author:** ![Ken-B](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ken-b/32/1780_2.png) [@Ken-B](https://discourse.julialang.org/u/Ken-B)\
**Post date:** [August 8, 2017, 8:34pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/3 "2017-08-08T20:34:08Z")

</div>

VS Code has become my primary editor now for julia packages, it’s really nice to use. I’m really looking forward to the integrated debugger feature.  
For interactive work I’m still using jupyter notebooks more often, even for package testing (maybe I’m not doing that part right…).  
Anyway, thanks a lot for all the great work and the amazingly quick bug fixes!

---

<div class="post-metadata">

**Author:** ![gdkrmr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdkrmr/32/2791_2.png) [@gdkrmr](https://discourse.julialang.org/u/gdkrmr)\
**Post date:** [August 9, 2017, 8:43am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/4 "2017-08-09T08:43:53Z")

</div>

I installed it on Ubuntu 16.04 to test it and observed the following problems:

1. The repository is often unavailable
2. The julia language server keeps crashing, I should have the latest tagged version of the language server and the julia language extension.
3. I have files in my home folder which I use for quick testing, e.g. `~/test.jl` and when I open them VSCode tries to parse everything in my home folder and consumes a lot of cpu time for a very long time.

---

<div class="post-metadata">

**Author:** ![mauro3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mauro3/32/292_2.png) [@mauro3](https://discourse.julialang.org/u/mauro3)\
**Post date:** [August 9, 2017, 9:02am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/5 "2017-08-09T09:02:36Z")

</div>

> [@gdkrmr](#):
>
> I have files in my home folder which I use for quick testing, e.g. ~/test.jl and when I open them VSCode tries to parse everything in my home folder and consumes a lot of cpu time for a very long time.

> <https://github.com/julia-vscode/julia-vscode/issues/201>
>
> Unfortunately, I tried to setup Julia support in VS Code and upon updating the j…ulia executable path to my Julia 0.6 binary, the language server process goes to 99% CPU indefinitely (until I kill it), confirmed by looking at Activity Monitor (on OSX). Any tips here? Anything I can load in the terminal to try and debug? This is my first attempt at using VS Code, so I really have no idea what's being attempted/loaded under the hood, so any direction would be helpful.

---

<div class="post-metadata">

**Author:** ![gdkrmr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdkrmr/32/2791_2.png) [@gdkrmr](https://discourse.julialang.org/u/gdkrmr)\
**Post date:** [August 9, 2017, 9:09am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/6 "2017-08-09T09:09:56Z")

</div>

on top of the julia process consuming 100% of one core, vscode consumes an additional 100-130%. The julia process gets killed by vscode with the message: “The jula Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.” and then does not consume any more cpu time.

---

<div class="post-metadata">

**Author:** ![mauro3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mauro3/32/292_2.png) [@mauro3](https://discourse.julialang.org/u/mauro3)\
**Post date:** [August 9, 2017, 9:24am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/7 "2017-08-09T09:24:19Z")

</div>

Do you have the setting “julia.executablePath” pointing to your Julia-0.6 install?

---

<div class="post-metadata">

**Author:** ![gdkrmr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdkrmr/32/2791_2.png) [@gdkrmr](https://discourse.julialang.org/u/gdkrmr)\
**Post date:** [August 9, 2017, 9:47am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/8 "2017-08-09T09:47:17Z")

</div>

yes, it points to the 0.6 install

---

<div class="post-metadata">

**Author:** ![mkborregaard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkborregaard/32/556_2.png) [@mkborregaard](https://discourse.julialang.org/u/mkborregaard)\
**Post date:** [August 9, 2017, 9:47am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/9 "2017-08-09T09:47:59Z")

</div>

As an intro, it’d be awesome to have a video demonstration. It appears the video supplier bungled the one from julia-con 17, but if you do another installment with a screen feed it would be a really nice resource.

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [August 9, 2017, 10:37am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/10 "2017-08-09T10:37:35Z")

</div>

@gdkrmr, that sounds like it’s not even starting up, could you open an issue on [github](https://github.com/JuliaEditorSupport/julia-vscode) and I’ll see if I can work out whats going on

---

<div class="post-metadata">

**Author:** ![jmgnve](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmgnve/32/1906_2.png) [@jmgnve](https://discourse.julialang.org/u/jmgnve)\
**Post date:** [August 9, 2017, 10:53am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/11 "2017-08-09T10:53:32Z")

</div>

Hi!

I don´t get an “Update to 0.7.0” option on VS code 1.12.1. If I remove the extension manually and reinstall it, it seems like it still installs the 0.6.2 version (or is the version tag in the red circle wrong?). See figure below. Anyone else experiencing this behavior?

 ![vscode](https://global.discourse-cdn.com/julialang/original/3X/d/e/deccbccdb34d85c94dc64cd1b00f5a3d943f2870.png)

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [August 9, 2017, 11:56am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/12 "2017-08-09T11:56:35Z")

</div>

You’ll have to update to vscode 1.14.+ to use the latest version I’m afraid

---

<div class="post-metadata">

**Author:** ![gdkrmr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdkrmr/32/2791_2.png) [@gdkrmr](https://discourse.julialang.org/u/gdkrmr)\
**Post date:** [August 9, 2017, 12:52pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/13 "2017-08-09T12:52:04Z")

</div>

@ZacLN: In the messages I can see the Language Server crashing, shouldn’t I open the issue in the Language Server repsitory? I guess that the other issues are not related to the Julia language support in VSCode, so they probably belong to other repositories.

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [August 9, 2017, 1:24pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/14 "2017-08-09T13:24:24Z")

</div>

In general opening issues on either repo is fine, although in this case I think it’s more likely a communication problem between vscode and the server.

---

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [October 22, 2017, 10:15am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/15 "2017-10-22T10:15:39Z")

</div>

Hello.

Do we need to install “Julia language highlight support” if we already have the extension “Julia 0.7” installed?  
What’s the difference between using “Julia extension 0.7” and “Code runner”?

---

<div class="post-metadata">

**Author:** ![wrgr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wrgr/32/2796_2.png) [@wrgr](https://discourse.julialang.org/u/wrgr)\
**Post date:** [October 22, 2017, 12:01pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/16 "2017-10-22T12:01:07Z")

</div>

> [@davidanthoff](#):
>
> extension will automatically detect whether that folder has a build, test or benchmark script

Could @davidanthoff please point on some examples of such scripts? Build/benchmark scripts is a cool feature, want to try.

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [October 22, 2017, 6:41pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/17 "2017-10-22T18:41:50Z")

</div>

If you open the Tokenize.jl directory in the vscode package directory you should be able to run the benchmarks

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [October 22, 2017, 11:27pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/18 "2017-10-22T23:27:15Z")

</div>

Hmm, I do have

```julia
"c:\\programs\\Julia-0.6\\bin\\julia.exe",
    "julia.runlinter": false,

```

but (annoying) Linter is still there. And furthermore it’s saying that `type` is deprecated, which is a 0.7 thing while I’m clearly declaring the path to 0.6

 ![Capture](https://global.discourse-cdn.com/julialang/original/3X/6/5/65d453ee19e12f5fabdd1b571d8e618f4419a03b.jpeg)

---

<div class="post-metadata">

**Author:** ![wrgr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wrgr/32/2796_2.png) [@wrgr](https://discourse.julialang.org/u/wrgr)\
**Post date:** [October 23, 2017, 5:12am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/19 "2017-10-23T05:12:10Z")

</div>

Thank you @ZacLN! So convention is that build scripts should be gathered into the top-level **build** directory alongside with **src** , **test** , **benchmark**? Would it work for nested, inside **src** , directories? Like some module will have it’s own **build** directory and scripts.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [October 23, 2017, 9:46pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284/20 "2017-10-23T21:46:51Z")

</div>

> [@Juan](#):
>
> Do we need to install “Julia language highlight support” if we already have the extension “Julia 0.7” installed?
> 
> What’s the difference between using “Julia extension 0.7” and “Code runner”?

The only thing you need is [this](https://marketplace.visualstudio.com/items?itemName=julialang.language-julia). The “Julia language highlight support” as far as I can tell is not maintained and I think the normal julia extension covers everything that one does. I don’t know Code Runner, but you don’t need it for the julia VS Code extension.

[Next page](https://discourse.julialang.org/t/vs-code-extension-v0-7-released/5284.md?page=2)