Closed ghost closed 10 years ago
The current addin does not support completly Xcode 5.0 (mainly because the XIB format has changed).
I have pushed a development version of the addin (the repository URL is http://addins.monobjc.net/devel/4.0/) that opens the project in Xcode 5.0 but it cannot parse the new XIB files. You have to manually add the outlets and the actions in the C# designer files.
I have started to work on a new parsing engine. I will update the issue as soon as something can be tested.
Hey letmiemble,
Thanks for that update!
Following some of the sample code and using your dev version I have been able to create my own designer code and get the outlets and actions working.
I really appreciate your help and fix!
Cheers,
Scott
PS: looking forward to the new parsing engine too. Cheers!
hey laurent, any news on Xcode 5 support?
I have uploaded a first version that supports Xcode 5 in the following repository: http://addins.monobjc.net/devel/4.2/
Hi there,
I have installed Mono, Monobjc, Xamarin Studio and the Monobjc add-in for Xamarin.
When I create a new Monobjc Cocoa Application I can't double click on the .xib file "MainMenu.xib" and get it to open the monobjc developer tools. I can open it by right clicking and selecting open with -> xcode but the problem then is the project is not synced in xcode so I do not have access to the delegate header file.
I wasn't sure if it was a Xamarin or a Monobjc issue but when I create a Monomac application double clicking the xib file opens up with xcode and syncs with xamarin sync correctly.
My current software versions are:
Xamarin Studio: 4.0.13 Mono: 2.10.9 Xcode: 5.0 Monobjc: 5.0.2165.0 Monobjc Development Add-in: 4.0.2167.11
OS: OS X 10.8.5
Sorry if there is a solution for this already. I had a look on the web and there was not very much helpful information. I tried restarting the applications, creating a new solution, and restarting the computer. I'm not sure what else I should try at this stage.
Thank you!
Scott.
Attached below is a screen cap of the error and a copy-paste of the full stack trace in the error.