Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 21667 [details]
Normally, XS opens a solution and shows the last state it was in when last opened; e.g., modules are open which were opened, left-hand solution tree nodes are expanded or collapsed as they were when last opened, etc.
Just a minute ago, it stopped do that. I've been switching between two different solutions as I am modifying one based upon things I had implemented in the other. I would open one, make a change and save it, go to "File > Recent Solutions" and select the other solution to open. I'd review some aspect of this solution (making no changes) and then go to "File > Recent Solutions" to open the original solution again to make a change.
At one point, it just opened the solution as though it had never been opened: solution tree nodes were all collapsed, no modules were open in the editor.
I closed and quit XS and then re-opened it and it is back to working correctly. I expect this was an anomaly but have attached the most recent IDE log regardless. If it happens again, I will update this case.
I'm not able to reproduce this, and your logs don't contain anything unusual. Changing status to NEEDINFO.
Please update this ticket if you manage to repro again. Thanks for the report.
I've had it happen again. I've yet to identify any particular pattern. No new info beyond that in the original report.
Hi, Rod! Thanks for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.1, and I was unable to hit the problem. I see that the issue keeps happening for you and I'll keep an eye out to see if I can eventually get a solid set of repro steps. If this issue occurs again for you, and you can identify a pattern, please reopen this report and attach the reproduction, ideally starting with a new template project and then showing the smallest number of steps needed to create the issue.