Bug 497 - Platform configuration should be "iOS" and not "iPhone".
Summary: Platform configuration should be "iOS" and not "iPhone".
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8 Alpha 2
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: ---
Assignee: mono-bugs+monodevelop@xamarin.com
Depends on:
Reported: 2011-08-28 15:11 UTC by Chris Hardy [MSFT]
Modified: 2012-11-15 12:57 UTC (History)
3 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 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:

Description Chris Hardy [MSFT] 2011-08-28 15:11:43 UTC
When working through the Building for Distribution tutorial (http://docs.xamarin.com/ios/tutorials/building_for_distribution) - we mention that the platform must be set to "iPhone". This is now out of date and the platform should be "iOS". This is especially confusing if people are building iPad applications where the platform isn't iPhone at all.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-29 05:38:10 UTC
iOS isn't really better, since it doesn't make clear that it's the device. Maybe "Device" and "Simulator" would be better.

Anyway, this is a nontrivial migration since it would potentially involve altering all the projects in a solution and the solution itself, and we we don't have a mechanism to do that.
Comment 2 Jeffrey Stedfast 2012-11-15 12:57:24 UTC
this is now fixed in ui-refresh