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 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.
In my project namespace structure, I use the platform name in the namespace. For instance, I have something like MyProject.App.MonoTouch to include all MonoTouch related application code.
When I created a custom ViewController in MonoTouch, and when I returned from Xcode to MonoDevelop, I could not open the .xib file again, because it prompts the error message: "Error updating Xcode project. Could not generate outlet 'myOutletName' in class 'MyProject.App.MonoTouch.MyClass' as its type '?' could not be resolved to Objective-C."
In the designer file (e.g. 'MyClass.designer.cs') the references to the UI controls are marked in red in MonoDevelop, except for the 'MonoTouch' part of the namespace.
When typing 'MonoTouch.' in the class, it shows the auto complete list for the project namespace, instead of the MonoTouch library namespace. Obviously, there is a namespacing conflict.
Therefore, the designer should create global namespaces (e.g. 'global::MonoTouch.UIKit.UILabel') if the automatically generated partial class is in a MonoTouch namespace (e.g. 'MyProject.App.MonoTouch').
How to reproduce the bug: create a MonoTouch project, save it with namespace 'TestBug.MonoTouch'. Then add a ViewController, add a label to the view controller, and create an outlet for the label. Then save and close Xcode. Then, try to open the .xib file again, it will prompt with an error message.
Vote 1 for this ... as fate would have it I have run in to the same problem as Bart at the same time
*** This bug has been marked as a duplicate of bug 1702 ***