You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The Code of ver 1.25 now has portable mode, when I enable the portable ,the Sync still download the settings/extens to userdata folder instead of the data folder within Code's folder.
Could it be fixed?
Thank you !
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Vscode supports portable mode since v1.25.
In windows, you can simply make a dir named data to enable portable mode , and all user data and extension will be placed in here.
As @waiaan said , in portable mode , the setting sync will cause an exception with message command 'extension.downloadSettings' not found.
Now in dev tool, we can see the c:\users\name\appdata\roaming\code\user\sync.lock not found
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The Code of ver 1.25 now has portable mode, when I enable the portable ,the Sync still download the settings/extens to userdata folder instead of the data folder within Code's folder.
Could it be fixed?
Thank you !
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: