We understand that many of you are experiencing difficulties integrating the STM32 extension into the Dev Container environment. Specifically, the extension is not functioning correctly due to a dependency issue message displayed in VS Code.
This problem arises from an extension installation issue within VS Code. This article lists the common issues, separate fixes, and a global workaround for all issues described below.
Issues and fixes
- When installing an extension and creating a Dev Container the extension is not automatically installed/imported to the Dev Container
- To add the needed extensions, you need to click on the cloud icon and select the extensions to be added to the Dev Container.
- The second issue appears after clicking on the cloud icon.
- The install process on the Dev Container is not stable, sometimes you may need to relaunch the process twice or three times to have all your extensions installed. - The third issue appears after adding all the needed extensions to the Dev Container.
- You may not be able to use them as VS Code is prioritizing the locally installed extensions, so to fix that you must disable the local extension to be able to use the instance in Dev Container.
The same issues and fixes apply if you are using different dev profiles.
Workaround
For a global fix to the previously described issues and to avoid fixing each issue with a specific fix you can use this workaround, by following these steps:
- Open your user settings
.jsonfile in the .vscode folder at the root folder of your project - Add the following code:
"remote.extensionKind": {
"stmicroelectronics.stm32-vscode-extension": [
"workspace"
]
}
Note: This is a workaround, and we are actively working with Microsoft to fix the issue.
We appreciate your patience and understanding as we work to improve your experience.
If you need any further assistance, feel free to reach out to our support team on the STM32CubeIDE for Visual Studio Code community.
