Bob Brown
Bob Brown
> Can this be fixed? > > [image] Yes, I think it should have the "Preview" part of the installation name, but it's missing. #resolved
> Can we align the setting name more with CMake Tools? > > [image] > > i.e. C_Cpp.persistVsDeveloperEnvironment ? > > i.e. "VsDeveloper" seems preferable to "Dev" since it's more...
> Can you add the command name? > > [image] > > It's possible the command may not have been invoked from the developer command prompt or in a way...
> FYI, it was able to set the developer environment when I didn't have a workspace open. Not sure what effect that has. > > [image] This feature adds to...
> I think it should just silently cancel instead of showing an error. > > [image] > > I think an error might be okay if it was an actual...
I'm going to put checkboxes and responses in your messages directly, since it's somewhat difficult to track these issues outside of comments directly in the code. I hope that's ok.
@sean-mcmanus I addressed your latest round of feedback.
> If VS Code is already launched from a particular VS developer command prompt, then the Set VS Developer Environment command is still available and runnable, but confusingly has no...
Ok, I did notice an oddity that I will need to debug. Something wrong did happen when the dev environment is already set and it does appear to fail to...
I have a fix for the "run from the developer command prompt" scenario in the node module. I just need to wait for it to show up in CFS so...