Quantcast
Channel: Category Name
Viewing all articles
Browse latest Browse all 5971

Visual Studio Code now available through Particle Workbench

$
0
0

We’re excited to announce that Visual Studio Code is included in the new release of tooling for Particle IoT developers. Developers using the Particle platform can now use Visual Studio Code as their default editor for building IoT apps!

Particle provides a widely-used IoT platform that consists of hardware, software, and connectivity. At their Spectra conference last year, Particle announced Particle Workbench, a professional IoT developer offering that includes Visual Studio Code.

Particle logo

Particle Workbench and Visual Studio Code provide a free, ready to use experience to develop, program, and debug apps on Particle’s IoT platform, as well as Microsoft Azure.

Particle Workbench and Visual Studio Code are available together through a single, downloadable installer, which include the toolchains and extensions for Particle’s IoT ecosystem, supporting local offline compilation and device programming, or cloud compilation and over-the-air (OTA) device programming. IntelliSense for Particle Device APIs are provided by Visual Studio Code language services and the C/C++ extension. Advanced hardware debugging is available in Visual Studio Code, for actions like setting breakpoints and step-through debugging, all pre-configured for Particle hardware. There’s also access to more than 3,000 official and community Particle libraries, enabling more reusability and less typing.

For more information, take a look at Particle’s announcement. And if you’re interested to learn more about how to use Particle with Microsoft Azure, learn how to create the dashboard of your dreams in this post from Paul DeCarlo.

Happy coding!

The post Visual Studio Code now available through Particle Workbench appeared first on C++ Team Blog.


Viewing all articles
Browse latest Browse all 5971

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>