- #Mamp pro transfer project to another computer upgrade#
- #Mamp pro transfer project to another computer code#
The Local Sync activity view is hidden by default and you can enable it using Views submenu under Settings Sync view overflow actions. You can open these views using Settings Sync: Show Synced Data command from the Command Palette. In case something goes wrong, you can restore your data from these views.
#Mamp pro transfer project to another computer code#
VS Code always stores local and remote backups of your preferences while syncing and provides views for accessing these.
#Mamp pro transfer project to another computer upgrade#
Once newer version of Stable build is released, you can upgrade your stable client and turn on sync to continue syncing. In such cases, Settings sync will be disabled automatically on stable to prevent data inconsistencies. Note: Since Insiders builds are newer than Stable builds, syncing them can sometimes lead to data incompatibility. This option is only available in VS Code Insiders. You can sync your Insiders with Stable by selecting the Stable sync service while turning on Settings Sync. Syncing Stable versus Insidersīy default, the VS Code Stable and Insiders builds use different Settings Sync services, and therefore do not share settings.
If at any time you want to sync your data to a different account, you can turn off and turn on Settings Sync again with different account.
entry in the Manage gear menu at the bottom of the Activity Bar. You can turn on Settings Sync using the Turn On Settings Sync.
Settings Sync lets you share your Visual Studio Code configurations such as settings, keybindings, and installed extensions across your machines so you are always working with your favorite setup. Configure IntelliSense for cross-compiling.