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.
Potential buglet? Jeff thought this might be an issue.
Steps to reproduce:
1. Start a new XamMac project
2. Start Xcode by double clicking the MainWindow.xib file
3. Add two widgets (button + label)
4. Create outlets for each in MainWindowController.h
5. Save the Xcode project
6. Return to MD
The updated designer file should correspond to the class that will be edited. (there should be a MainWindowController.designer.cs under MainWindowController.cs)
The MainWindow.designer.cs file is updated.
The only thing that really matters here is what existing users expect and what our docs say to do, so filing as minor for now.
I just noticed this today actually. I think this is a regression in the addin as we used to have MainWindowController.designer.cs. I haven't touched the addin in months, so I don't know what changed. The first time I noticed this is under XS 4.0.8.
I thought it always added it to MainWindow.designer.cs? Maybe not... I never really paid attention.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.