Bug 40070 - "Can't change the solution property while debugging" when plugging in phone
Summary: "Can't change the solution property while debugging" when plugging in phone
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: vsx
Depends on:
Reported: 2016-04-03 15:36 UTC by Tom Gilder
Modified: 2016-04-22 17:05 UTC (History)
4 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 Tom Gilder 2016-04-03 15:36:30 UTC
Plugging in an iPhone whilst debugging results in a Visual Studio dialog: "Can't change the solution property while debugging".

This is whilst using Windows on a Mac via Parallels Desktop.

Steps to reproduce:

1. Start with no devices plugged in the the mac
2. In Visual Studio, start debugging an app on the iOS simulator
3. Plug in an iPhone to the Mac

I assume Xamarin is trying to change the startup device to the physical iPhone.

Visual Studio 2015 Update 2 v14.0.25123.00 
Xamarin (a78562a)
Xamarin.iOS (3dd8da4)
Comment 1 Daniel Cazzulino 2016-04-22 17:05:01 UTC
Thanks for this very helpful and detailed bug report.

We've identified the root cause and implemented a fix that 
will be available in a future release (4.2.x time-frame 
most likely).