recovery tag data #640
-
Hello, I use the bookmark under the window to store the tags of the remote code, but now the ip address of the remote server has changed, so my bookmarks are gone. How can I restore the data, or go there to find the data information stored before? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
tag description also save in state.vscdb? i did't found it. |
Beta Was this translation helpful? Give feedback.
-
I found that the C:\Users\Administrator\AppData\Roaming\Code\User\workspaceStorage directory is a single temporary file. Is there a file that stores all the data? Does the plug-in perform data recovery based on so many db files? |
Beta Was this translation helpful? Give feedback.
-
Hi @sourcema , The extension stores the bookmarks per workspace (which is a VS Code concept) and when you rename / move it, VS Code will understand it as a new workspace. For remotes, it't s the same concept, and if the IP of the remote you are connected (via SSH for instance) changes, it will be recognized as a new workspace as well. That's the reason why aren't seeing the bookmarks from the original IP. In the old days, the bookmarks were stored inside VS Code itself (Local Storage) and were accessible using DevTools, but it's been a while the data is stored locally: var appdata = process.env.APPDATA || (process.platform === "darwin" ? process.env.HOME + "/Library/Application Support" : "/var/local");
appdata += "/Code/User/workspaceState"; Inside the Unfortunately, there is no solution to recover the data using the extension. But, there are alternatives to not happen anymore
Hope this helps |
Beta Was this translation helpful? Give feedback.
Hi @sourcema ,
The extension stores the bookmarks per workspace (which is a VS Code concept) and when you rename / move it, VS Code will understand it as a new workspace. For remotes, it't s the same concept, and if the IP of the remote you are connected (via SSH for instance) changes, it will be recognized as a new workspace as well. That's the reason why aren't seeing the bookmarks from the original IP.
In the old days, the bookmarks were stored inside VS Code itself (Local Storage) and were accessible using DevTools, but it's been a while the data is stored locally: