# Two Configuration Questions about Julia in VSCode

**URL:** <https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913>\
**Category:** General Usage\
**Created:** [January 6, 2021, 1:56am UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913 "2021-01-06T01:56:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TI36XPro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ti36xpro/32/33658_2.png) [@TI36XPro](https://discourse.julialang.org/u/TI36XPro)\
**Post date:** [January 6, 2021, 1:56am UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913/1 "2021-01-06T01:56:45Z")

</div>

Hello,

I have two questions regarding Julia and the Julia extension for VS Code.

Coming from C++, I know I can use things like `tasks.json`, `c_cpp_properties.json`, and `launch.json` to configure my code compilation, its execution, debugging, etc.

From reading around it seems I can still use `launch.json` to establish my debugging options (like opening an integrated terminal on session start). And I think I’ve also determined the following:

- `Tasks.json` is not necessary or used for Julia. The extension comes with its own commands for building and running the code. Did I get that right?
- Should or can I create `julia_properties.json` like I did for c++?

I’d appreciate a peer check and any thoughts/comments.

Thank you!

---

<div class="post-metadata">

**Author:** ![TI36XPro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ti36xpro/32/33658_2.png) [@TI36XPro](https://discourse.julialang.org/u/TI36XPro)\
**Post date:** [January 13, 2021, 4:24am UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913/2 "2021-01-13T04:24:59Z")

</div>

Could we have this moved to “Tooling”?

---

<div class="post-metadata">

**Author:** ![CameronBieganek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cameronbieganek/32/6915_2.png) [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)\
**Post date:** [January 13, 2021, 4:40am UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913/3 "2021-01-13T04:40:53Z")

</div>

I don’t have the definitive answers to your questions, but as far as I know there is no need for a `tasks.json` file or a `julia_properties.json` file when using the Julia VS Code extension.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [January 13, 2021, 10:14am UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913/4 "2021-01-13T10:14:28Z")

</div>

Yes, there shouldn’t be any need to add custom tasks or a `julia_properties.json` (whatever that would do).  
In general we have `Julia: Execute ...` commands that use the integrated REPL to run your code and `Debug/Run File in new process`, which you can probably customize in `launch.json`.

---

<div class="post-metadata">

**Author:** ![TI36XPro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ti36xpro/32/33658_2.png) [@TI36XPro](https://discourse.julialang.org/u/TI36XPro)\
**Post date:** [January 13, 2021, 12:11pm UTC](https://discourse.julialang.org/t/two-configuration-questions-about-julia-in-vscode/52913/5 "2021-01-13T12:11:04Z")

</div>

Thanks for the responses!
