setting variables via local-view should use the variable path -> error shown with optfde01
While it seems reasonable to me to try to add this extensions' features to a maintained vsix extension (I'd personally try to do this to the native-debug extension, if it is accepted there) I think it is useful to still fix some outstanding issues, including this one.
It can be seen in the optfde01 sample.
Currently the assignments just use the name of the variable they are applied on, which will often not work and create a "multiple symbols match" issue. The fix seems to be relative easy: use the full path of the variable (if not known create it when reading in the nodes).