Bug 25738 - Visual Studio hangs while loading the iOS project without connecting to build host
Summary: Visual Studio hangs while loading the iOS project without connecting to build...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.8
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Prashant manu
Depends on:
Reported: 2015-01-06 06:13 UTC by Prashant Cholachagudda
Modified: 2015-09-29 03:12 UTC (History)
5 users (show)

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 Prashant Cholachagudda 2015-01-06 06:13:29 UTC
When we start Visual Studio 2013 Update 4 and load the solution without having a connection to a build host the IDE freezes and even after minutes of waiting the IDE does not return to a working state.  And it is noticed that this always happens during the load of the iOS project.

Logs: https://www.dropbox.com/sh/d07s9ki3mhjdlbw/AAAIFLzQynYQnQVEVDwpYwp3a?dl=0
Comment 1 Enzo Heredia 2015-09-28 14:11:04 UTC
This is no longer happening with latest build from master or alpha. Please verify
Comment 2 mark.allibone 2015-09-29 03:12:30 UTC
I can no longer reproduce the issue on Visual Studio 2015, working off master branch. From my end the issue seems to be solved.