NRF Connect Extension Pack loses Workplace toolchain setting

[Anthony Ambuehl]

I would like to maintain an isolated sdk and toolchain for a specific project.  I used toolchain manager to install the sdk and toolchain into a new installation directory.  I  started VS Code from tool chain manager and was able to find chain the workplace settings for the SDK and toolchain to the new installation directory.  However every time I go back to the "Open Welcome Page" in nrfConnect or when I review the workplace settings in preferences I see the original Nordic toolchain installation directory instead of the new one that I have assigned in the workplace settings.

Specfically in the Workspace settings I see ${nrf-connect.toolchain:2.3.0}

I have tried entering the path to the toolchain in Workspace settings and also selecting it from the drop down page but it keeps going back to the orignal Nordic installation.

Is this a known bug or is there something I need to do to save the workspace settings?

[ovrebekk]

Hi 

Which version of the SDK and the toolchain are you trying to use? 

There is a known issue if you use a toolchain that is considered too old for the SDK you are using. In this case the toolchain version will be overwritten every time you open the welcome page. 

This will be patched in a future update, but unfortunately this update is still a while out. 

In the mean time the best workaround would be to either make sure you use the same toolchain and SDK version, or to avoid opening the welcome page. As you probably know a lot of the same features are available through the Welcome tab of the extension interface:

Best regards
Torbjørn

[Anthony Ambuehl]

I just installed the 2.3.0 toolchain and sdk last week.   I  am not mixing toolchain version, I'm trying to isolate the tool chain from different projects.  The issue is that for this project it may be necessary to modify the toolchain and I do not want those modification to affect other projects. 

Since this issue is happening with the latest version of VS with latest release of NRF Connect extension pack, I'm reporting this bug so it can be fixed.

The Welcome tab is where I am setting the workspace toolchain and where I later confirm that the value I changed has reverted back to the user settings instead of the workspace settings.   

Is the root cause of the bug...that opening the welcome tab is automatically changing the toolchain?  

[ovrebekk]

Hi 

So if I understand you correctly you have two parallel v2.3.0 SDK installations on the same drive but in different locations, each with a separate 2.3.0 toolchain included? 

Anthony Ambuehl said:

Is the root cause of the bug...that opening the welcome tab is automatically changing the toolchain?  

Essentially yes, but this bug should not happen if the SDK and toolchain versions are identical. 

I will try to reproduce the issue locally, and forward your findings to the developers. 

Best regards
Torbjørn

[Anthony Ambuehl]

Yes that is correct.  I have 2 identicial toolchains installed by toolchain manager.  However VS keeps reverting to the initial installation and not the one I have selected for the workspace.

[ovrebekk]

Hi 

Thanks for the clarification. 

I was able to reproduce the issue on my side, I see that the second SDK installation keeps wanting to use the toolchain from the original SDK. 

I will report this to the developers and ask if this is something they can look into. 

As a workaround in the mean time it should be possible to manually select the right toolchain each time you open the workspace. Can you confirm whether or not this is working?

Best regards
Torbjørn

[Anthony Ambuehl]

In preferences..settings..User   I unchecked Welcome: Show On Startup

In preferences..settings..Workspace   I changed Toolchain: Path

after restarting visual studio, the workspace toolchain setting was maintained.