Greg, that's a long and confusing thread - things that work seem to be at
the very end of it. Interesting that it applies to VS2010 (your problem with
VS2012). 

Did you mean this: 

I have found that I can export my current settings, then reset all settings,
then import selected settings, but exclude the window layouts (General
Settings > Window Layouts) and it works. If it works, it's much less
disruptive than resetting all your settings. Tuesday, September 06, 2011
2:19 AM MichaelCsikos

Or the simpler

the only thing that worked for me, and which is pretty simple is:

open the cmd.exe

type "devenv /resetsettings"

it will restart visual studio and my files were saved again afterwards

Wednesday, April 18, 2012 9:31 AM Electrocution

  _____  

Ian Thomas
Victoria Park, Western Australia

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Greg Keogh
Sent: Saturday, August 24, 2013 4:42 PM
To: ozDotNet
Subject: Visual Studio forgets opened files

 

Just a quick follow-up on this problem from last week. After bumbling around
in web searches I eventually came upon THIS
<http://social.msdn.microsoft.com/Forums/vstudio/en-US/dfe4100a-6228-46ab-89
f3-5c3c05ab5098/visual-studio-2010-ultimate-doesnt-remember-previously-opene
d-files> . I exported by settings, reset them, then imported all settings
except Windows Layouts and it's looking okay. I suspected something like
this would solve the problem, but I couldn't face hours of experiments to
try the various combinations. Luckily someone did it first. I'm actually
sceptical that omitting the Windows Layouts was critical to the fix, as
perhaps the reset step simply fixed things, but I can't waste time trying to
find the exact fix steps.

 

Also, months ago I had changed VS2012 settings Environment > Import and
Export Settings > Automatically save my settings to this file ... to point
to a file on a network shared drive letter which was regularly backed up.
After running the reset steps above and running VS2012 as Admin I was
getting a file access error because the network shared letter was unknown to
admin. I changed it to \\unc <file:///\\unc>  format and fixed the problem,
but it's weird I never saw that error in previous months.

 

Greg K

Reply via email to