David, I ran more experiments on my dev machine and on a spare VM with
VS2013 and I have solid evidence that the problem is machine specific. All
solutions, old and new, in my dev machine that were closed with a WPF
designer open will reopen with all windows closed.

The problem does not occur in VS2013 on my spare VM. Doing a devenv
/resetsettings has no effect. Running as admin or user has no effect.
Deleting suo files has no effect. I recall it started happening something
in the last two weeks, but I can't link it to anything memorable that
happened.

So unfortunately I can't give you any useful information to help diagnose
the problem. I will keep an eye on it and let you know if I can report
anything useful.

Cheers
Greg K


On 27 January 2014 16:40, David Kean <[email protected]> wrote:

>  I can’t repro it Greg, I’m trying a WPF project with the designer open
> and the same windows open when I repro the solution in VS2013. Can you call
> out the exact steps that it takes to repro and I’ll get a bug filed.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Jano Petras
> *Sent:* Sunday, January 26, 2014 5:01 PM
> *To:* ozDotNet
> *Subject:* Re: Visual Studio 2013 forgets open files
>
>
>
> Well investigated Greg. As there are Microsoft people on this list, lets
> hope that this bug will find its way to the right destination.
>
> On Monday, 27 January 2014, Greg Keogh <[email protected]> wrote:
> > Folks, over a year ago I reported this problem with VS2012 where it
> forgot while files were open when I reopened a solution. This disease
> returned in recent days to VS2013. The previous fix of exporting all
> settings (except Windows layout), reset then import has no effect. Deleting
> suo files has no effect.
> > I spent the last half hour fiddling with this and the problem seemed
> intermittent. Further experiments reveal that the problem ONLY happens when
> I close a project with a xaml file open in the designer. If I do so, all
> windows are closed when I reopen the solution. Leaving any xaml designer
> open is the specific cause of the problem. There are no useful search hits
> on this and I can't find a fix so far.
> > Greg K
>

Reply via email to