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?

[Betta Sharma]

I think I may be having some problems similar to what this thread mentions. I do not understand the 'workplace' concept well. Where is it documented? I do have my west CLI, nRF, .vscode extensions all in different folders and I think they are not recognizing each others directory paths properly. Is there a set of 'Registry' files to understand how these paths are being accessed and interpreted? Specifically, I am getting an error "Multiple West Workplaces" and I do not understand this message nor how to resolve this. I am using Windows 10. Zephyr v3.7.99, Zephyr SDK 0.16.8, VS Code 1.95.3

[runsiv]

Hi

As this case over two years old. Please create a new case with the same information, also include the NCS version 

Regards

Runar