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.
I would like to request a feature that will automatically disconnect other VS instances from the build host (if they are not running) and then establish the connection on the current VS instance so that I could continue to run build. That would streamline the flow and save me a lot of solution loading time (especially if the solutions are quite large).
I have two visual studio solutions, SolA and SolB. Both of these are VS2012 Xam iOS projects.
I open SolA in VS and it connect to mac build host, and start debugging it runs the iOS simulator just fine.
I stop the debugging in SolA.
I open SolB in VS, and here I cannot start debugging because it does not allow me to connect to the mac build host. It tells me the mac build host is unreachable.
The current work-around for this is that I close SolA and then SolB will allow me to connect to build host to then start debugging.
I would like to avoid having to close solutions and reopen them again just to run the build on another VS instance.
@email@example.com Close the solution doesn't work for you?
When VS closes the solution the connection should be closed.
Closing the solution actually works but my solution is composed for more than 70 projects and opening it takes me more than 2 minutes. I usually works with another very basic solution aside when I am trying to identify problems in my complex projects. I try to extract the problem and reproduce it in a basic program. Systematically having to close one solution and reopen the other is a great lose of time for me. Moreover I cannot see the code of my two solutions at the same time.
The current BuildHost (3.11) already has a disconnect button which allows the user to manually disconnect VS from the BuildHost in Solution A, and using Refresh Build Host on the other VS instance (Solution B) you can connect it to the Build Host without the need of closing and reopening solutions.
This behavior is actually present since 3.8 IIRC, but the bug didn't get updated.
Hence, I'm closing the issue.
Thanks for the report!