You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
When you select your active configuration with IAR status toolbar, Intellisense doesn't update iar-vsc.json.
To Reproduce:
Open a workspace with more than 1 configuration. It open with "CONF_1".
Change configuration to "CONF_2" with status bar, iar-vsc.json does'nt update : Close VS, reopen your project, it is opened on configuration "CONF_1".
If you change configuration from IAR-BUILD sidebar, all it's aok, iar-vsc.json is update, and reopen the project on the last configuration.
Expected behavior:
At reopen of project : Last configuration is selected
Actual behavior:
At reopen of project : always the same configuration is selected
Environment:
OS: Windows 10
Embedded Workbench: Arm
Embedded Workbench version: 9.20
VSC Extension version: 1.30.6
Additional context:
Status bar :
Sidebar :
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! We've fixed the issue, so it should work as expected in the next release. Until then, you'll have to use the sidebar if you want the configuration change to be saved to disk.
Describe the bug:
When you select your active configuration with IAR status toolbar, Intellisense doesn't update iar-vsc.json.
To Reproduce:
Open a workspace with more than 1 configuration. It open with "CONF_1".
Change configuration to "CONF_2" with status bar, iar-vsc.json does'nt update : Close VS, reopen your project, it is opened on configuration "CONF_1".
If you change configuration from IAR-BUILD sidebar, all it's aok, iar-vsc.json is update, and reopen the project on the last configuration.
Expected behavior:
At reopen of project : Last configuration is selected
Actual behavior:
At reopen of project : always the same configuration is selected
Environment:
Additional context:
Status bar :
Sidebar :
The text was updated successfully, but these errors were encountered: