Visual Studio corrupts its settings with regular monotony (it always did, I suffered from this since Visual C ++, and this is still a bug in VS2013).
Often this seems completely random, but it is very likely after the crash.
It will also lose any changes in your settings if Visual Studio doesn't turn off cleanly - for some reason, instead of saving the settings when you are OK in the dialog box, VS seems to wait until it closes your entries, so after changing the settings I always leave and restart to make sure that the changes have been flushed to disk. Similarly, you should never change the settings with two or more instances of VS, since the last one to exit will overwrite the settings.
In particular, there is an easily reproducible case: if you run two or more copies at the same time (by this I mean, if you run two or more copies, therefore they are all initialized at the same time), they seem to be fighting for the settings file, and it becomes damaged or reset to default.
The best two workarounds I've found are:
Never run more than one instance at a time. If you need to run several instances at the same time, then wait until the first one finishes downloading its solution before you start the next one.
Always use Tools > Import and Export Settings to save your settings to a backup file, so recovering from this damage takes only a few seconds every time this happens.
Another small, but still rather annoying habit is that if VS is minimized when it shuts down (for example, disconnecting), it distorts the location information of the window, and at the next start it will be maximized.
Jason Williams Sep 09 '14 at 21:52 2014-09-09 21:52
source share