After a project is added to the local VSCode workspace, right click on the Project in the Project treeview (not File Explorer) and select the Remove option.
The dialog shows Remove, Delete, Cancel.
Remove deletes the folder from the local VS machine.
Delete deletes it from the remote DS device.
Cancel should do nothing.
But Cancel may (not always!) remove the project from its current "active" project status - thankfully without deleting any files.
To be clear, I can click Cancel and the project remains active, or I can click Cancel and the project "disconnects".
We need a Disconnect or Deactivate option rather than just Remove.
This leaves the existing folder in the local workstation, leaves the DS device project, and "forgets" the current location of the VS/local folder. This is how the Cancel option "usually" works now. We just need this to be clear and explicit behavior.
After a project is added to the local VSCode workspace, right click on the Project in the Project treeview (not File Explorer) and select the Remove option.
The dialog shows Remove, Delete, Cancel.
Remove deletes the folder from the local VS machine.
Delete deletes it from the remote DS device.
Cancel should do nothing.
But Cancel may (not always!) remove the project from its current "active" project status - thankfully without deleting any files.
To be clear, I can click Cancel and the project remains active, or I can click Cancel and the project "disconnects".
We need a Disconnect or Deactivate option rather than just Remove.
This leaves the existing folder in the local workstation, leaves the DS device project, and "forgets" the current location of the VS/local folder. This is how the Cancel option "usually" works now. We just need this to be clear and explicit behavior.