Bug 12222 - Fail to Launch the Debugger after Change the Active Platform.
Summary: Fail to Launch the Debugger after Change the Active Platform.
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 0.x Insider Preview
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Vinicius Jarina
Depends on:
Reported: 2013-05-13 12:13 UTC by Vinicius Jarina
Modified: 2013-05-31 08:35 UTC (History)
6 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 Vinicius Jarina 2013-05-13 12:13:38 UTC
Fail to Launch the Debugger after Change the Active Platform.

If the Active Platform is iPhone Simulator and you change to iPhone and try to Start Debug right after change, VS tries to start the Debugger on a iPhone Simulator instead iPhone Device.
Comment 2 Mohit Kheterpal 2013-05-31 08:35:10 UTC
Today we have checked this issue on following builds :

VS 2010 / 2012
MTVS 1.1.103
MONO 2.10.12

Now when we select iPhone simulator in active platform after deploying application on  iPhone then application deploy to simulator and when we select iPhone after deploying application on simulator then its deploys on iPhone device. 

Hence this is working fine. Changing its status to verified.