Bug 18381 - Paring with multiple MSVC (UX)
Summary: Paring with multiple MSVC (UX)
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.12.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Enzo Heredia
Depends on:
Reported: 2014-03-14 00:00 UTC by Virgile Bello
Modified: 2015-08-03 17:02 UTC (History)
8 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 Virgile Bello 2014-03-14 00:00:33 UTC

We would like to be able to switch more seamlessly between multiple opened VS instances.

Best option would be to have a single Mac Build host handle multiple MSVC instance.
However, I understand this might be impossible on your side (due to Apple restrictions?).

If impossible, it should at least be much more easy to switch MSVC instances.
Let's say I have two solutions opened (either 2 on my own computer, or me + another developer) and I would like to switch.
Currently the workflow is:
1. Go on the MacOSX (VNC or physical computer)
2. Unpair (to force disconnect the previous user)
3. Pair
4. In VS2012, enter the PIN code

I can think of two options to solve this problem:
1. A disconnect button, so that we don't have to go through the painful cycle of closing VS and opening another one when we want to work on two solutions at the same time.
2. Allow a "force connect" which would kick current user on the build host (usually in a cooperative dev team, this should be fine). Maybe that should be an option to configure on the build host?

Comment 1 Virgile Bello 2014-03-14 00:02:39 UTC
BTW, those two options should be on MSVC side so that we don't have to touch the build host (which could be a headless computer). i.e. there could be a force disconnect other user button in the VS toolbar.

Also, in the current workflow, I forgot to mention that step 4 (PIN code in VS2012) also involves many clicks/keys to press, network ack, so it takes quite some time every time.
Comment 2 Udham Singh 2015-08-03 11:16:14 UTC
This issue has been fixed with latest XMA builds (XVS + X.iOS, now we can connect multiple VS to a single build host.

For now I am marking this issue as Resolved-Fixed.

Comment 3 Enzo Heredia 2015-08-03 17:02:28 UTC
this is verified,