Bug 49162 - Default to "iPhoneSimulator" as the Platform in the ConfigurationManager
Summary: Default to "iPhoneSimulator" as the Platform in the ConfigurationManager
Status: RESOLVED DUPLICATE of bug 45942
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Templates ()
Version: 4.3.0 (C9)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Pierce Boggan [MSFT]
Depends on:
Reported: 2016-12-06 23:04 UTC by Pierce Boggan [MSFT]
Modified: 2017-03-02 19:19 UTC (History)
5 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 Pierce Boggan [MSFT] 2016-12-06 23:04:24 UTC
When opening an iOS project in Visual Studio, the default is currently to show "iPhone" as the Platform in the configuration manager. We should default to iPhone Simulator, as this is what most people are going to be doing during development. It's also confusing to new users who don't understand why when they build for the iPhone target nothing shows up in the iOS Simulator (either on Windows or Mac).
Comment 1 Pierce Boggan [MSFT] 2016-12-07 00:03:04 UTC
This also makes the build time much longer.
Comment 2 Ben Beckley 2016-12-07 15:33:27 UTC

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