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.
During the changes (add an Outlet for example) from Interface Builder the xib.designer.cs file doesn't change, then I don't find my element in the xib.cs file.
If open the xib file, the new element was correctly saved, but doesn't appear in the designer class
MonoDevelop 2.8 introduced a new xib designer model in order to support Xcode 4.
The Interface Builder integrated in Xcode 4 no longer supports defining classes, outlets and actions in xib files, therefore MonoDevelop can no longer generate *.designer.cs files from xib files.
In our new model, the *.designer.cs files are where the outlets and actions are defined. When you open the xib file, MD creates an xcode project with objective-c stubs to allow Xcode 4 Interface Builder to use the types. Any changes you make to these types in Xcode are then imported back into the designer files in MD.
Unfortunately, this is not backwards-compatible with Interface Builder 3 codebehind. Our recommendation is that you switch to Xcode 4.
Please see http://docs.xamarin.com/ios/tutorials/transitioning_from_xcode_3_to_xcode_4
@alan: I would've closed it - but you decide.