Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
As Unified API is a preview release, it should not be the default template when creating a Xamarin.iOS project.
### Reproduction Steps
1. Open Visual Studio
2. Select New Project
3. Navigate to iOS
4. Notice Classic API is nested with Unified API projects prominent
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Installed Version: Professional
Xamarin 184.108.40.206 (8ca7d11db8a6f874c6cd2de6d9ca0f511867ce91)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 220.127.116.11 (5474129af31e9d3a86cb7482c7c5c7a30ad315f1)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 18.104.22.168 (209abebbd8f1a292d042420edb45fa5fbd3f017b)
Visual Studio extension to enable development for Xamarin.iOS.
I would also request that if you flip these and make the Unified API the tested ones under the defaults and the defaults are the Classic API that you also prefix the nested folder name with "Preview" and each of the Unified API templates with "Preview". Having it in the description isn't enough to make sure it gets noticed.
Also I would argue that anything you label as preview is incomplete and should not be part of a stable release channel until you are willing to remove the preview label. However at least making sure its not default is better than the current state, although not ideal.
changed "tested" to "nested" in previous comment.
I am alos seeing the same behavior. This is the screencast for the same: http://www.screencast.com/t/LMmKRdmt
I mark this issue as fixed since Unified and Classic separation doesn't exists anymore