I’m trying to make the shift to VS Code as my Particle code editor. I’ve followed some tutorials on the web, but can’t find the process for how I include particle libraries in my VS Code project? Is there some setup in VS Code that maps to a github or url to get to the libraries? Or is this a mute…

Did you delete all library files that were not inside the lib folder? During your first attempt via particle copy library you may have added some files that are now giving you grief. Maybe start a new project completely fresh.

When using CLI for building you just need to add a dependency entry into the project.properties file to instruct the build server to also use the library files stored there already. This way you won’t need to download the library sources into your project just in order to re-upload them for buildin…

thanks @ScruffR this really helped point me in the right direction. I got it working and I’m compiling now in VS Code. couple of observatoins, if anyone else wants to pursue this. I was using PowerShell and this did not work to add the dependencies into project.properties. I used Node.js command …

Hey Brian, just in case it improves your already working setup in any way: [image] Use Visual Studio Code for your Particle development needs Tutorials Hey, if you are a fan of Visual Studio Code I wrote an article on how to use it to build and flash your Particles in Hac…

I like using Particle Desktop IDE. However, not having Atom’s “Go To Declaration” work is starting to become a issue for large projects with many files. VSC is far superior to Atom, and the problem with trying VSC, is that we have to install CLI. Every time I have installed CLI on a PC I will get BS…

[image] seulater: However, not having Atom’s “Go To Declaration” Hi, I can confirm that Go To Declaration works in VS Code. Now, if there is NO WAY to get out of the BSOD you mention on Win10 (is it a general problem?) I would go the docker way. In the case you are familiar with docker, ther…

[image] gusgonnet: Hi, I can confirm that Go To Declaration works in VS Code. Yup, and so does code peek. I have been slowly migrating over to ESP32, and It's actually funny you mention "...configure a task in VS Code that calls a script to compile..." because I had to do the same thing for V…

[image] seulater: So thanks for the turning on the light bulb. cool! :bulb: Please, if you don't mind, post back what you do so I learn too about your experiments.

[image] gusgonnet: Please, if you don’t mind, post back what you do so I learn too about your experiments. Not sure when I will get around to trying on Particle. I did make a video on how to do it with the ESP32, maybe something there can help in the meantime. [ - YouTube]

so I tried to install libraries following your instructions. In VSC, in the left side, I click the particle logo, then CLI I type ( following CLI instructions ) particle library add google-maps-device-locator particle library add Ubidots I then open project.properties I then see dependenc…

well, some little time off and I think I simply need to do this in CLI particle library copy Ubidots particle library copy google-maps-device-locator [EDIT] NOPE, does not work. :unamused:

Visual Studio Code IDE - Particle Development setup

Firmware Libraries

gusgonnet August 28, 2017, 8:10pm 4

Hey Brian, just in case it improves your already working setup in any way:

cheers!
Gustavo.

Topic		Replies	Views
Use Visual Studio Code for your Particle development needs Tutorials	44	13870	March 17, 2019
Particle CLI integrated with Visual Studio Code General	3	1454	October 3, 2018
Adding libraries to project - local and public ones Getting Started	51	5180	December 14, 2018
Particle libraries Libraries	13	1151	December 4, 2021
Need help with file structure for particle (Visual Studio) Libraries	6	1733	June 27, 2017

Visual Studio Code IDE - Particle Development setup

Related topics