Reopen Documents on Solution load not working since upgrade to 16.9

Art Hansen 566 Reputation points
2021-03-13T12:46:46.1+00:00

Since upgrading to 16.9 VS is not reopening on Solution load the files that were open at shutdown (I always use File -> Exit).

I've verified "Reopen Documents on Solution load" is checked in Options and the solution's .vs folder has been deleted (and successfully rebuilt automatically by VS).

While my solution is small (only about 60 files) it is still quite irritating to start a VS session reopening a number of related winform designer & code documents plus the supporting class library and sql/textfile connection documents. In addition to being a waste of time I have come rely on the auto relopening to immediately refresh my memory regarding exactly what I was working on at shutdown.

Any ideas in addition to what I've already tried will be much appreciated.
Art.

Windows Forms
Windows Forms
A set of .NET Framework managed libraries for developing graphical user interfaces.
1,839 questions
Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,647 questions
{count} votes

Accepted answer
  1. Art Hansen 566 Reputation points
    2021-03-18T08:21:41.31+00:00

    @Dylan Zhu-MSFT Using the built-in VS problem reporting (Thanx Dylan) I discovered there have been over a 128,000 reported incidents of this bug.

    According the incident being worked (1317364) this is supposed to be fixed in version 16.10 which is currently classified as Pending Preview Release. Not being privy to the release roadmap I don't know the target date for pushing out a generally available 16.10.

    Until that release is available the only partially viable work-around is to close any "tear-off tab" windows prior to Exiting the solution/VS. That will at least enable re-loading of docs in the main VS window on the next solution load.


6 additional answers

Sort by: Most helpful
  1. Ron Clabo 36 Reputation points
    2021-10-08T15:16:17.31+00:00

    I found a fix!

    I'm experiencing the same issue with VS 2019 and have been experiencing it for maybe months. Today I finally decided to look into it because having VS forget the windows I had open everyday when it launches is sooooo frustrating and time wasting. I'm running the latest version which is currently 16.11.4 (just updated a few days ago). I am running the Community edition but I suspect the issue is systemic and probably occurs in all editions.

    By deleting the .vs hidden directory inside by solution folder and forcing VS to rebuild the info it keeps in that folder (it rebuilds it automatically if it's been deleted), now VS is working like normal and when I close VS with several windows open, it will open them back up on next launch.

    7 people found this answer helpful.

  2. Art Hansen 566 Reputation points
    2021-03-16T07:32:23.913+00:00

    @Dylan Zhu-MSFT Thanx for taking the time to respond.

    No, I am not trying to prevent the reopening; I want to "re-enable" the reopening function which I find very useful.

    On further investigation I have determined the "reopening not occurring" is happening for one -- and only one -- of my solutions. It is the largest and most actively worked on. It stopped properly reopening for this single solution when I upgraded VS Community to v16.9 and the subsequent upgrade to 16.9.1 has not fixed the problem.

    Since the problem is only occurring on one solution the cause must be at the solution level. The only unusual action I've taken was to close VS manually while downloading the 16.9 upgrade rather than waiting for the upgrade process itself to automatically close VS...

    Best Regards,
    Art

    1 person found this answer helpful.

  3. Dylan Zhu-MSFT 6,406 Reputation points
    2021-03-15T08:38:39.987+00:00

    Hi ArtHansen,

    While my solution is small (only about 60 files) it is still quite irritating to start a VS session reopening a number of related winform designer & code documents plus the supporting class library and sql/textfile connection documents. In addition to being a waste of time I have come rely on the auto relopening to immediately refresh my memory regarding exactly what I was working on at shutdown.

    Do you want to prevent visual studio re-opening files which are in last session? If so, please disable "Reopen Documents on Solution load" and "Restore Solution Explorer project hierarchy state on solution load".
    77762-image.png

    Best Regards,
    Dylan


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our **documentation to enable e-mail notifications if you want to receive the related email notification for this thread.**

    0 comments No comments

  4. Art Hansen 566 Reputation points
    2021-03-17T06:43:02.717+00:00

    @Michael Gossett Thanx Michael - your input prompted me to look at the problem differently.

    As preface, I just upgraded/updated to 16.9.2 (that's the 3rd in about a week so I strongly suspect the upgrade development team either missed their deadlines or lost testing personnel) and it still hasn't fixed the problem.

    2nd preface, this is NOT restricted to a single solution as I erroneously stated above. It is confirmed to be at the VS level.

    I do not run multiple monitors but instead have a single large screen on which I can see more than two full size windows side-by-side. My setup is [1] main VS window: split horizontally w/code in top and winforms in bottom, [2] a 2nd window equal in size to the main VS window: not split, contains code, and [3] a 3rd small window displaying errors etc. & TODO content.

    Exiting VS with all 3 windows open results in only windows [1]and [3] being displayed and NO documents being reloaded on VS restart/solution load.

    Closing window [2] prior to VS exit results in open documents being reloaded per expectation on VS restart/solution load.

    This was tested on multiple solutions with identical results regardless of solution scope or scale.

    TO MSFT READERS: I understand that users of the Community version neither pay for not are entitled to tech support for a "free" product but I still think this should be escalated up thru your management chain. This seems to clearly be a bug and a fairly obvious one.