Is Xamarin Studio absolutely necessary for the release of Mono apps on the Mac App Store and MonoMacPackager obsolete?

There was a time, not two years ago, when you didn't need Xamarin.Mac to deploy Mono apps on the Mac App Store . To be clear, this storage is for Mac OS X desktop applications, not iOS apps.

Now the MonoMacPackager page says the following :

If you want to create stand-alone Mac packages or publish your software on the Mac AppStore, you should get Xamarin.Mac, which is a strict superset of MonoMac.

I have not seen a good tutorial on how to release on the Mac App Store since the release of Xamarin.Mac. Is Xamarin.Mac a "must-have" release, so to speak, of Mono applications on Mac that have user interfaces written in Xcode / IB? Or is it the “subset” that MonoMac is still enough to create these hybrid applications?

I understand that I can write against GTK # or Windows.Forms, and users can install Mono themselves - or use bockbuild , as Banshee still does and has something self-sufficient - to create stand-alone applications. Instead, I'm interested in using the Mono interface with native user interfaces created in Xcode and for releasing these applications on the Mac App Store.

Xamarin Studio, . , .

, MonoMacPackager Mono , Mac App Store?

+4
1

, Mac App Store . , mkbundle, , , , Mono . - LGPL.

LGPL, Xamarin.Mac.

, , LGPL, : , ? , ToS Mac App Store GPL/LGPL.

, ... .

. , , mkbundle, . ( : Mac App Store , AppStore iOS, .)

+5

All Articles