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.
This is a feature request regarding the Build host: basically I have a stationary Windows Machine which I use for regular work (& which is paired with my Xamarin Build Host on my Macbook Pro), but whenever I take that later macbook pro on the go and work on the road / outside the office, I boot up a VMWare hosted Windows instance on that very same machine and well - have to do the whole pairing again to pair that VMWare Windows + Visual Studio installation with the very same build host.
.. And whenever I am back in the office do the same again - pair the desktop with the build host.. and again.. and again. Kind of cumbersome.
It would be really, really great if one build host would support multiple paired clients.
According to my initial question on your forum, this pairing problem is not only per machine but also for the exact same client machine with multiple VS instances running in parallel (see http://forums.xamarin.com/discussion/comment/52090/#Comment_52090).
Cheers & thanks,
As per the final comment on the thread, you don't need to repair every time, you can reuse the same code from your stationary machine and your vm. So you should not need to repair again.
Running multiple instances of VS against a single build host is currently not supported.
I second this request, but with extra features.
We have multiple developers using Windows and would like them to use a single build host. The host would build and run for each developer showing an emulator for each.
The developers would be able to remote in to the server and chose their emulator to show as a window on their desktop.
Any official response to Jason Steele's feature request? I'm trying to sell Xamarin.Ios on my next project and this feature alone would save us enough money in hardware that it would easily justify the Xamarin licenses.
Running multiple VS against one Mac would really save money on our side.
We are also very very interested in having a build host that handles more VS connections
We have multiple developers on windows boxes who would like to run against a single mac mini we have in the office.
The issue was marked resolved, are there any details available?
I made a private comment, didn't realised you can't see it.
we re-wrote the way that this works for stability and quality reasons, can you try our alpha release as this should resolve your request.
This does not seem to me like it is resolved. We have a similar set up to the one described on this thread. We have multiple windows computer that use visual studio to connect the a build host running on an IMac that's in the network. An we multiple visual studios are trying to use the build host one of them gets disconnected and has problem establishing a connection.
Is there a plan to get something to solve these problems?
This will only work as long as each connecting user has a distinct Mac user name.
If it doesn't work, please provide repro and logs.
Also, make sure each Mac user account is logged in on the Mac.