-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to use pre-installed vscode in installer. #307
Comments
We're not going to allow installing into a stock VS Code through the installer automatically. We do some other customizations as well, including turning off updates. There have been cases in the past where a VS Code update has broken the WPILib extension. Having a single setup also makes debugging when teams have issues much easier. However, the customization thing actually gives a decent idea. We could pretty easily import the configuration from a previous years VS Code, which would allow you to hold customizations year after year. |
I think that just keeping customization from a previous years installation would be a viable solution, but I am wondering if this would also install the extensions that were separate from the wpilib ones into the new vscode instance. |
Yes it would. I'd just be making a copy of the data folder. Which should work. |
Shouldn't this be transferred to the installer repo? |
When I have to re-install wpilib after an update it frustrates me that all of my customization is left on the old version, and that it uses extra space to my current vscode installation. I think that a good solution would be for in the installer to ask if you want to add all of the extensions to a pre-existing vscode installation. I have been just installing the *.vsix files into vscode, but it would be more convenient to just have it automagically install them if the option is selected in the installer.
The text was updated successfully, but these errors were encountered: