Bug 11370 - If a Xarmarin.iOS/MonoTouch Universal project has a target device of iPad set when the solution is loaded it will still load the iOS simulator in iPhone mode, not iPad mode.
Summary: If a Xarmarin.iOS/MonoTouch Universal project has a target device of iPad set...
Status: RESOLVED DUPLICATE of bug 11101
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0.3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-03-23 07:19 UTC by Dave
Modified: 2013-03-25 16:49 UTC (History)
1 user (show)

Tags:
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 or GitHub 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:
Status:
RESOLVED DUPLICATE of bug 11101

Description Dave 2013-03-23 07:19:32 UTC
If a Xarmarin.iOS/MonoTouch Universal project has a target device of iPad set when the solution is loaded it will still load the iOS simulator in iPhone mode, not iPad mode.  

In order to get it run in iPad mode i have to switch the target device to a different item and then back to iPad mode and run the application again.
Comment 1 Jeffrey Stedfast 2013-03-25 16:49:59 UTC

*** This bug has been marked as a duplicate of bug 11101 ***