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.
Created attachment 6236 [details]
When you open a .xib the following class will not have a header file accessible from Xcode:
public class Foo : UIView
private const string ClassName = "Foo";
The result is that you can't set up outlets/actions from Xcode with this class. The same class would have a header file in Xcode if you replace Foo.ClassName with the literal string "Foo".
I would like either approach to work because I want to avoid making a typo in the string (it may appear in multiple places).
To reproduce open the attached project and then double click on one of the .xib files. Notice that in the resulting Xcode project there is a header file for RegisteredWithLiteral, but there is not a header file for RegisteredWithConst.
I have checked this issue with attached project on below environments:
XS 4.2.3 (Build 59)
X iOS 18.104.22.168
I have checked this issue with attached test project and followed steps as mentioned in bug description, I opened .xib file in Xcode and noticed that both "RegisteredWithLiteral" and "RegisteredWithConst" header file displayed on Xcode. Refer screen cast: http://screencast.com/t/E45CGbzla
Looks like it was fixed in a later Xamarin Studio (or Xamarin.iOS?). I was holding back on upgrading because of another issue with provisioning profiles, but that appears to be fixed now as well (not sure when that happened...).
Sorry for the noise!