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 for Bug 30711 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Creating new a project for MonoMac does create a project which does not compile. It yields the error for MainWindow and MainWindowController:
The Type or namespace name 'AppKit' does not exist in ... do you miss an assembly reference?
I would expect the IDE to create a compilable project from the dialog.
Tested on Mac OS X 10.10.3 with Xamarin Studio 5.9.2 (Build 4)
@sjoerd - Can you provide steps to reproduce?
When I create a MonoMac or Xamarin.Mac Classic application, I get a buildable project that references using MonoMac.AppKit;
When I create a Xamarin.Mac Unified project, I get a buildable project that references using AppKit;
I cannot reproduce doing the following:
Start Xamarin Studio. Create new Solution. Create new project. Select Othe(Miscellaneous: MonoMac (Open Source)/Cocoa App (C#).
But I can reproduce with:
Checkout the repo Xilium.CefGlue (bitbucket). Open Xamarin. Open the solution. Right-click on the solution and click Add New Project. Select again MonoMac (OpenSource) / Cocoa App (C#).
Now the build fails with the error: "The type or namespace name 'AppKit' does not exist ..."
So it happens on an existing solution. Would there be a reason for this to happen due to some solution settings? (I would not expect that)
This type of issue is better handled on the forum, as it is a "why is this not working", not a "this is broken, and here is proof".
But to answer you question. The "raw" namesakes, like
are only in the Unified Xamarin.Mac projects.
In the (unsupported) open source MonoMac bits and Xamarin.Mac Classic, it is
I was not looking for an answer and your answer is completely unrelated. The IDE in fact creates the project with the correct using directives.
I wanted to report that if you add a MonoMac (OpenSource) project to an existing solution it will not create a compilable project which I would expect from the IDE.
Creating a project in an empty solution on the other hand gives you a compilable project.
I am sorry if I was not clear enough.
@sjoerd I'm having trouble reproducing you issue. Could you attach a solution showing the issue.