Bug 10500 - Default target for iOS project
Summary: Default target for iOS project
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: 4.2.3 (from master)
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-02-21 02:38 UTC by Maxim
Modified: 2014-01-03 11:53 UTC (History)
2 users (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:
VERIFIED FIXED

Description Maxim 2013-02-21 02:38:12 UTC
When I first opened existing project in X.S, it setup default target as "iPhone Simulator 5.0".

I prefer it choose "iPhone Simulator 6.0", cause project uses 6.0 SDK.

Note: project uses 6.0 SDK, yet it's Deployment Target is 5.0. Maybe since now X.S uses Deployment Target for the first project open.
Comment 1 Mikayla Hutchinson [MSFT] 2013-02-21 03:36:12 UTC
It's arguable which simulator is more useful TBH.

With the 6.0 SDK you can build apps that will run on any version up to 6.0, it's up to you to gracefully check for version specific APIs etc. If you do support older OS versions, you would set the deployment target to the older version you support. So really, you need to test your app on both versions, and the versions in between.
Comment 2 Maxim 2013-02-21 04:57:19 UTC
You're right, that is not a bug, but it's about preferable behavior.
I could check it right now, but seems like in MD it's was not as now in X.S.
Comment 3 Jeffrey Stedfast 2013-02-22 13:12:31 UTC
I think the way the configuration dropdown works is that it simply defaults to the first item in the list, which will always be the lowest iOS version supported.
Comment 4 Mikayla Hutchinson [MSFT] 2013-02-22 16:15:41 UTC
We could still do this. Maybe an IsDefault property on ExecutionTarget - or the project could simply return them in reverse order.
Comment 5 Jeffrey Stedfast 2013-02-22 18:40:50 UTC
I'm not saying we can't do it, just saying how it seems to work now :)
Comment 6 Jeffrey Stedfast 2013-10-29 17:32:40 UTC
the newest simulator version is now the default instead of the oldest
Comment 7 Mohit Kheterpal 2014-01-03 11:53:38 UTC
Today we have checked this issue with following builds :

XS 4.2.3 (build 24)
X.iOS 7.0.6.166

Now when we create new iOS application then latest version of simulator is available.

Screencast : http://screencast.com/t/fYvcWjjooBR

Hence closing this issue.