

It's usage is much trickier for a Windows developer you should better understand native Mac development at least a little and it would be good to understand Objective-C, at least the basic ideas: Objective-C - Wikipedia, the free encyclopedia. Monobjc - Wikipedia, the free encyclopedia, To develop such native interface, you can use another product, Monobjc: Yes, but they won't be compatible with Windows. Even when you successfully develop correctly working Windows Forms application, it will look foreign on Mac in particular, you will see that the standard Mac menu on top of the desktop is shown as always, but is unrelated to your application, which may have it's own main menu, like in "normal" Windows Forms applications.Ĭan you develop Mono applications to behave natively on Mac. Now, more problems: Mono is good for many platforms, but Apple platforms is notoriously hostile to the "foreigners". MonoDevelop - Wikipedia, the free encyclopedia,

SharpDevelop - Wikipedia, the free encyclopedia, If some code works well on Mono for Windows, additional problems with Mono for other platforms are much less likely.

This way, you can do essential inner development cycle on Windows only. NET and then testing it for Mono for Windows, and, in case of incompatibilities, fix them and test on Mono again. One nice way to do development on Windows would be developing and testing everything on. However, you will face some incompatibilities. NET, Mono for Windows, or Mono for Mac, without recompilation. In all cases you can use the same assemblies for. NET or Mono, Visual Studio, or SharpDevelop, or MonoDevelop IDE. Then you can develop the applications on either Windows, or MAC.

You can do it if you install Mono, the alternative CLR implementation, on Mac OS X: Mono (software) - Wikipedia, the free encyclopedia.
