Using Visual SourceSafe's "Open SourceSafe Database..." command, there is an option at the bottom of the dialog to "Open this database next time I run Visual SourceSafe."
Typically, when checking this box the most recent opened VSS DB is opened immediately upon launching VSS (even if it's a second instance of VSS running).
I'm seeing this option not respected. All launches of VSS result in the same DB being opened at launch.
Removing all the registry entries under HKLM\Software\Microsoft\SourceSafe\Databases and HKCU\Software\Microsoft\SourceSafe\Databases doesn't help.
Additionally, the HKCU\Software\Microsoft\Sourcesafe\Current Database value was accurately pointing to the DB I wanted to be opened, but not the DB that was VSS was actually opening. Same with the similar value under HKLM.
An environment variable had been set to force that particular database.
When SSDIR is set, the VSS dialog option is ignored.
Clearing the SSDIR variable fixed the issue.
Related
I'm using VSCode with the devcontainers feature. I recently made a large update to my devcontainer configuration, moving the devcontainer from a single DockerFile to docker-compose.yaml. Everything's working fine except that and I'm finding every time I start up the devcontainer, VSCode shows a toast notification in the bottom right corner informing me that the devcontainer "Configuration file(s) changed...The container might need to be rebuilt to apply the changes."
If I select the provided option to rebuild the container, I'm still presented with this same message the next time I open VSCode and start up the devcontainer. Basically, VSCode thinks the configuration files for the devcontainer were changed every time I open the devcontainer, even though they haven't been changed since I last built the container.
At the moment, this is just a very minor annoyance--the devcontainer works fine and all I need to do is ignore the toast notification once on startup. It appears as though something is going wrong though. Does anyone have any idea as to why VSCode might be showing this message each time I start up the devcontainer? Or better yet, how to address this message in a better way than simply ignoring it?
I want VSCode to always open the same folder when I launch it. The current behavior is to launch whatever folder VSCode thinks I last visited.
I maintain notes that are kept in folders on the same system that I run my local VSCode instance from. All of my development is on remote systems that are often not running when I launch VM. In a development session, I often have many (5-10) files open in VSCode on various source, config, and data files -- often on multiple remote systems. These remote systems are frequently not even running when I next launch VSCode.
When I launch VSCode, I want VSCode to always open (from the desktop) my local "notes" folder, where I keep my daily journal files. I want to then open folders on remote systems -- most often using the "File -> Open Recent" command.
I do not see anything in settings.json or in preferences that lets me control what folder is open on startup.
How do I configure VSCode so that it always opens the same (local) folder on startup, regardless of what files I was editing when I last closed it?
I'm working on an application in vscode whose behavior is impacted by the settings of a handful of specific environment variables (the three "proxy" variables). I'm doing this on an Ubuntu VM.
At one point I realized that I had to change the settings (clear them) in order for my application to work. I know that it can be challenging to change env vars in subprocesses, so I decided to keep it simple and simply restart the entire VM after I changed my .profile. After the restart, I checked a shell window and the vars were set as I wanted (not set). I then started up vscode from my Ubuntu favorites bar. In the terminal window I printed the values of those vars. They still had the values I set before. I verified that when I ran the application from vscode (not from the terminal window in vscode), it behaved badly, so it was using the old values. In the terminal window, I then manually cleared those variables to put them into the correct state. I manually ran the service from the terminal window, and it did what it was supposed so, reflecting the cleared variables.
It appears that vscode is storing environment settings on disk and never getting them from the parent shell again.
How do I control this behavior?
So the latest version of vscode (1.46) provides preference sync, but I found I cannot enable this feature for remote vscode. Whenever I open remote folder, (e.g., in wsl), the option to sign in MS account and turn on preference sync is missing. Did I miss anything here or it is not supported?
figure below shows my local vscode instance with the preference sync:
figure below shows my vscode instance for remote (wsl) without the preference sync option:
https://code.visualstudio.com/docs/editor/settings-sync
I was looking to enable this too, the first line is the answer I think. Only available for vscode insiders at the moment, maybe wait 'til next month
What I want is to have all of my workplace preferences reset every time I quit VS Code. Right now, if I quit the application and opened the same folder I previously closed, VS Code still retains all pointer positions and all opened files. This maybe good for a lot of people, but for me, I just feel overwhelmed.
What I have tried:
I tried to locate .vscode folder but it is non-existent in my project folder.
"Clear Command History" doesn't work.
"Clear Editor History" doesn't work.
Following this link ---> https://github.com/Microsoft/vscode/issues/42948 and deleting /home//.config/Code/Local Storage doesn't work.
Following this link ---> https://github.com/Microsoft/vscode/issues/42948 and running window.localStorage.clear() in Electron development console returns undefined.
I am using Ubuntu 18.04.
In the settings menu you can search for window.restoreWindows and change that to none. You can also change workbench.editor.restoreViewState to false which might also help.