Skip to main content
Version: 6

IDE Extension


For Torizon OS 6, the v1 Visual Studio/Visual Studio Code extensions are no longer supported. The recommended development environment for TorizonCore 5 and Torizon OS 6 is the Torizon IDE Extension 2 (formerly codenamed ApolloX on Toradex Labs).

Torizon IDE Extension 2​

From feedback and past experience, Toradex redesigned the Torizon Extensions, from scratch, to better integrate with Torizon OS, delivering a improved developer experience. Now the Torizon IDE extension 2 uses the Docker Visual Studio Code extension with your remote Torizon device and simplifies the Docker images, container and volumes management during the development cycle.

Also, the new version comes with a new collection of templates, that already configure and automate the VS Code tasks needed to cross-compile the application, build a Docker image and deploy it on the Torizon remote device. It also attaches the VS Code to a remote debugger, thus speeding up the application development process.

Documentation Summary​

Development Workflow​

  1. Set up the Torizon IDE Extension 2 Environment
  2. Create a Single-Container Project
  3. Connect a Torizon OS Target Device
  4. Remote Debug and Deploy Projects
  5. Add Packages, Libraries and Tools to Existing Projects
  6. Pass Arguments to Containerized Applications
  7. Build and Push Applications
  8. Update Project from Template
  9. Programming Languages Documentation Overview

CI/CD Workflow​

  1. CI/CD - Configure Projects to Run CI Pipelines
  2. CI/CD - Integrate With GitHub Actions
  3. CI/CD - Integrate With GitLab CI Pipelines

Extra Resources​

  1. Troubleshooting
  2. Reference Documentation Overview

Feature Overview​

The following table contains a preliminary feature comparison between the two versions of the extension.

FeatureTorizon VS/VS Code Extension V1Torizon IDE Extension 2
Target Device OS SupportTorizonCore 5Torizon OS 6
Host OS SupportLinux
Ubuntu 22.04
Debian 11 ("bullseye")
Windows (via WSL 2)
IDEs SupportedVisual Studio
Visual Studio Code
Visual Studio Code
Supported use casesC/C++ (single-file with direct GCC call, Makefile, Autotools, CMake, Qt 5 headless, Qt 5 Widgets, Qt 5 QML)
Python (console, Qt 5 Pyside 2 Widgets, Qt 5 Pyside 2 QML)
C#/.NET (console, ASP.NET + Angular, ASP.NET + Blazor, ASP.NET MVC, ASP.NET + React, ASP.NET + React + Redux, Uno Platform)
From Toradex:
C/C++ (Makefile, Qt 6 QML)
Python (console, Qt 5 Pyside 2 QML)
C#/.NET (console, Uno Platform)
From the community:
Rust (console)
Java (Swing JFrame)
Node.js (console TypeScript, Electron Javascript)
.NET/C# (Mono 4.7 Windows Forms, Uno Platform, Avalonia)
Visual Basic (Gambas3 Forms)
full updated list on GitHub
WorkflowDocker related details are abstracted and are not easily edited manually.
Remote debugging application on Torizon device is possible.
Only one container can be worked on per project at a single time.
Docker details are now more transparent.
Auto-generated files like Dockerfiles can be manually edited allowing greater flexibility.
Remote debugging application on Torizon device is possible.
Multiple container projects are now possible allowing multi-container solutions to be developed and debugged in parallel more easily.
ArchitectureClient-server type architecture where the backend interfaces with the IDE through a REST API.Libraries written in TypeScript using a more scripted approach to tasks compared to the previous model.

Send Feedback!