Bug 52904 - Opening and existsing Xamarin.Forms project (iOS, Android, UWP with a shared project and a PCL project) causes Visual Studio to crash.
Summary: Opening and existsing Xamarin.Forms project (iOS, Android, UWP with a shared ...
Status: RESOLVED DUPLICATE of bug 52695
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: --- blocker
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-02-28 16:34 UTC by Brian Campbell
Modified: 2017-02-28 17:05 UTC (History)
5 users (show)

Tags: Cycle9R
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 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.

Related Links:

Description Brian Campbell 2017-02-28 16:34:09 UTC
# Steps to reproduce
Open a Xamarin.Forms solution created before installing the Cycle 9 Stable update

# Expected behavior
Successfully load all of the projects in the solution

# Actual behavior
Only the iOS, PCL and shared projects open. VS hangs with "(loading)" shown next to the solution, Android and UWP project names.

# Supplemental info (logs, images, videos)

# Test environment (full version information)
Latest version of VS2015 and Xamarin on Windows 10 (fully updated)
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2017-02-28 17:05:31 UTC
I will tentatively mark this as a duplicate of Bug 52695 based on the similarity of the reported symptoms.

## Next steps

1. If you get a chance, you can try the candidate fix in the patched build as linked in Bug 52695, Comment 31.

2. If that build does _not_ resolve the issue, please collect and attach back (on this bug, Bug 52904) a minidump from the frozen instance of Visual Studio by attaching to it from a second instance [1], and then saving the minidump _without_ heap [2] (so it'll be of a manageable size).

[1] See steps 1-5 on https://developer.xamarin.com/guides/cross-platform/getting_started/visual_studio_with_xamarin/troubleshooting/vs-callstack/

[2] After you have paused the debugger via "Debug > Break All", choose "Debug > Save Dump As" and use "Save as type > Minidump (*.dmp)".  See also "Create a dump file" on https://msdn.microsoft.com/en-us/library/d5zhxt22.aspx

Thanks in advance!

*** This bug has been marked as a duplicate of bug 52695 ***