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 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.
With some projects it just goes:
Build server control connection failed
Mono.IOS.VisualStudio.MonoTouchPackage Error: 0 : Server 10.0.0.10 hung up
connection. Unable to read data from the transport connection: A blocking
operation was interrupted by a call to WSACancelBlockingCall.
[2014-01-04 19:26:40.0] INFO:Found Xcode, version 5.0.2 (3335.32).
[2014-01-04 19:26:40.6] INFO:Found Xamarin.iOS, version 220.127.116.11.
Mono.IOS.VisualStudio.MonoTouchPackage Warning: 0 : Build server returned an
Mono.IOS.VisualStudio.MonoTouchPackage Warning: 0 : Negotiating server
information for pairing process.
[2014-01-04 19:27:10.7] monotouch.xml
[2014-01-04 19:27:10.7] OpenTK.xml
[2014-01-04 19:27:10.7] MonoTouch.Dialog-1.xml
[2014-01-04 19:27:11.1] MonoTouch.NUnitLite.xml
[2014-01-04 19:27:11.1] NamespaceSummaries.xml
and stays there. Same "works" on vs2010 ( slow as hell, but at this point I understand you're not going to fix that...)
So, can't use VS 2013...
I am not able to reproduce this issue with VS 2013. We have tried with different Android and iOS template and successfully build them with VS 2013.
Could you please attach the sample project/test case which you are not able to build in VS 2013?
As most other connection bugs for VS, this too comes and goes. It's now gone for the moment.
I just hope the VS plugin gets enough attention to become robust and avoid all these bug tracking.
Will get back when/if it happens
When/if that happens, do not kill the VS session but instead attach to it using a different VS instance, then break the hung instance's execution by ctrl-break in debugger and then post the call trace here.
I think this only happened right after installing VS2013 alongside VS2010 . Somehow I think VS2010 (which was close) kept the build host busy, which is consistent with other bugs regarding updating where the devenv.exe process is kept open by Xamarin plugin (I think).
For me it's ok now after uninstalling the plugin for both, rebooting and reinstalling it