Bug 23964 - Change the File -> New -> iOS template structure to match Xamarin Studio for Unified projects
Summary: Change the File -> New -> iOS template structure to match Xamarin Studio for ...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.7
Hardware: PC Mac OS
: High major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-10-21 14:04 UTC by John Miller [MSFT]
Modified: 2015-04-01 09:03 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 John Miller [MSFT] 2014-10-21 14:04:30 UTC

   The current File -> New Project -> iOS menu does not have the unified project templates nested under Unified API like Xamarin Studio does. This causes confusion and mistakes when creating a new projects. Users are choosing the Unified API templates by mistake because they are more obvious to select then expanding Classic API first. 

**Expected Results:**

   Unified templates should be nested in a Unified API menu option (similar to how Classic API templates are nested) similar to Xamarin Studio so the choice is more obvious.
Comment 1 Joaquin Jares 2014-10-22 17:17:01 UTC
Our goal is to have users use unified api. Starting next year Apple will only accept packages that include a 64bit version. So as stated before, this is by design.
Comment 2 Miguel de Icaza [MSFT] 2014-11-19 10:29:30 UTC

This is correct, but the setting should only be done when the iOS Unified API stabilizes, and right now it is not stable.   We are not freezing that API until next week.
Comment 3 Joaquin Jares 2014-11-19 11:35:25 UTC
I didn't know that. This is the way it's been since iOS8 shipped (and Unified was included). Does it make sense to change it now?
Comment 4 Prashant manu 2014-11-24 02:26:37 UTC
Checked, currently Unified API menu option (similar to Classic API templates are nested) doesn't exist.
Screencast: http://screencast.com/t/w9n7pHdDGK

Environment Info:
All VS
Xamarin (10cfd178d55287f09c85f5a1e604dfe20889a40f)
Comment 5 Joaquin Jares 2014-11-24 06:45:31 UTC
As discussed with Miguel via Hipchat, this is not an issue and will not be fixed.