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
Today, the (favorite) projects are stored in a file called projects.json. It is stored in VS Code internals, and you have the possibility to use a different location via projectManager.projectsLocation setting, if you need, for instance, share the projects with other VS Code release or even to sync using any sync service.
The idea of this issue is to allow the user to store their projects in User Settings, as an alternative to the projects.json file concept. It's not meant to_combine_ projects.
Issue #525 asks for projects to be stored in GitHub Gist, in order to allow sync, since Settings Sync won't allow external files to be synced. Issue #712 asks for multiple values to projectsLocation, (which raises a few concern, like how to know in which of the projects.json file a new project should be saved). So, storing the projects in the User Settings would solve, at least, the settings sync support.
The text was updated successfully, but these errors were encountered:
First of all, for me, the development projects configured on different office computers are different, such as doing my own projects at home and doing the company's projects in the company. In this way, the directory where the management project is located may be different. For example, in the company, the D disk "project" of Windows is used. The project is stored, and the mac used at home is stored under desktop/repos. So if you want to synchronize, I would like to ask if this situation is currently supported?
Feature: Another idea is: Does it currently support the "git remote url" for backing up the project in projects.json when storing the project? In this way, even if the project does not exist when I click on it after synchronization on other computers, I can get the project from the git address. If it can be like this, it will be absolutely great!
Today, the (favorite) projects are stored in a file called
projects.json
. It is stored in VS Code internals, and you have the possibility to use a different location viaprojectManager.projectsLocation
setting, if you need, for instance, share the projects with other VS Code release or even to sync using any sync service.The idea of this issue is to allow the user to store their projects in User Settings, as an alternative to the
projects.json
file concept. It's not meant to_combine_ projects.Issue #525 asks for projects to be stored in GitHub Gist, in order to allow sync, since Settings Sync won't allow external files to be synced. Issue #712 asks for multiple values to
projectsLocation
, (which raises a few concern, like how to know in which of theprojects.json
file a new project should be saved). So, storing the projects in the User Settings would solve, at least, the settings sync support.The text was updated successfully, but these errors were encountered: