After installing STM32Cube for Visual Studio Code, why do two icons appear on the left panel?

[Nov4ou]

Hi, I followed the instructions in this post to install the STM32Cube extension for Visual Studio Code. After completing the installation, I noticed that two icons appeared in the left panel: one labeled "STM32Cube" and the other "STM32 VS Code Extension".

The difference is that under "STM32Cube", there is only a "Key Actions" menu instead of the Project Manager, so I can’t import my project. On the other hand, the "STM32 VS Code Extension" icon works correctly and allows me to import my CMake project.

Which one should I keep?

[vincent_grenet]

@Nov4ou 
I would advise restarting the VSCode instance (it is good practice after installing or removing a new extension).
Let us know if this solves the issue.

[Nov4ou]

Thanks for your reply!
Unfortunately, restarting VS Code didn’t solve the problem. It looks like installing “STM32Cube for Visual Studio Code” also automatically installs the “STM32Cube for Visual Studio Code Core” extension. However, according to the installation guide I followed, the Core extension was meant for older versions. Why is it being installed together with the newer preview version?

 

[vincent_grenet]

The STM32Cube for Visual Studio Code Core extension is fully expected and essential as part of the fresh extension pack proposal.
Only the STM32Cube for Visual Studio Code extension contributes to the activity bar icons (left panel, see https://code.visualstudio.com/docs/getstarted/userinterface).

Having the STM32Cube butterfly icon twice is almost impossible by design, but if you experience this, I admit I have encountered it occasionally. Usually, the cause is an issue with VSCode itself during extension updates.

If restarting does not solve the problem, your VSCode extension cache is likely corrupted.

A soft recovery method is to uninstall all STM32Cube extensions via the VSCode GUI, restart VSCode, and then reinstall the STM32Cube for Visual Studio Code extension pack (only this one the rest is going to be pulled for you).

If this does not help, a hard recovery involves clearing certain cache folders. This is considered hard because you may lose some settings.

 

[Nov4ou]

Hi,

After deleting my previous VS Code profile and creating a new one, I reinstalled the extensions. The issue with duplicate icons is now resolved. However, a new problem appeared:

In the left panel, the "Project Manager" entry has disappeared and is now replaced by "Key Action". Unfortunately, there’s no option to import a CMake project anymore.

In the current version of the extension, how can I import a project? I also couldn’t find documentation describing the latest version’s behavior.

[vincent_grenet]

Thanks @Nov4ou for confirming that VSCode may be the usual suspect. I’m happy to see you up and running now!

Since you’re using the fresh proposal, I can confirm that the CMake project import feature is no longer promoted as a shortcut or explicit action. But no worries: CMake is still fully supported! This new approach aims to embrace a more vanilla VSCode workflow. We have introduced features that work behind the scenes to achieve the same result.

Let me explain the philosophy:

VSCode users typically add folders to the workspace rather than clicking an import button. For example, Microsoft’s CMake Tools extension automatically discovers CMake projects and runs the initial configure process when a folder is added. We have adopted the same approach for STM32Cube.

We ensure STM32Cube does not interfere with your existing CMake workflow because many users rely on CMake for other projects. We fully support the Microsoft CMake Tools extension and let it operate as usual. On top of that, we offer an optional service to enhance your CMake project with STM32Cube features. You decide:

• If you don’t want STM32Cube features, simply reject the proposal: STM32Cube won’t bother you.

• If you accept the STM32Cube add-on, welcome!

Here’s how to try it:

1. Add your CMake project folder to the VSCode workspace.

2. Wait for the automatic process to run, which should trigger a notification.
   

3. When you see the notification, click “Yes” to accept.
   
   

If you miss the notification, you can always trigger the process manually using the dedicated action.

I also suggest exploring some useful documentation related actions.