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.
Created attachment 14929 [details]
Visual Studio & XMA logs
Similar to the issue encountered in this case:
Renaming / Refactoring a custom View Controller isn't reflected in the storyboard. I was able to reproduce this as follows:
1. Create a new iOS Single View app (comes with a storyboard and a ViewController already.)
2. Open ViewController.cs, and refactor the class definition of "ViewController" to a different name, like "AnotherViewController"
It seemed like the references to the ViewController were renamed everywhere except for the storyboard itself. The ViewController in the storyboard did not seem to be updated accordingly. I also didn't see the warning ("yield") sign you referred to, though perhaps that was due to my test case being very minimal somehow. (Nothing really depended on the bits I changed.)
## Build Information
Microsoft Visual Studio Community 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA601
Microsoft Visual Basic 2015
Visual C# 2015 00322-20000-00000-AA601
Microsoft Visual C# 2015
Visual C++ 2015 00322-20000-00000-AA601
Microsoft Visual C++ 2015
Windows Phone SDK 8.0 - ENU 00322-20000-00000-AA601
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET and Web Tools 2015.1 (Beta8)
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 14.0.50616.0
Microsoft SQL Server Data Tools
TypeScript for Microsoft Visual Studio
Xamarin 184.108.40.206 (dcea9c1)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 220.127.116.11 (e98e962)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 18.104.22.168 (47eb74b)
Visual Studio extension to enable development for Xamarin.iOS.
I agree that this isn't a bug, but I also think it's not the best user experience. I can't really think of a scenario where you would refactor the UIViewController class name, but wouldn't want the value in the codebehind updated. I'm not sure we can really control that, as this part of the refactoring engine is out of our control. Our best bet may be something like a lint rule that will look for inconsistencies between a registered class name and it's _actual_ name.