Hi, what I would like to be able to do is to develop an API (library, not app) on top of MonoTouch, then distribute this API to my users.
Now, if I create a library (dll) using MonoTouch and give this to a user, does that force them into using MonoTouch as well? What if, for whatever reason, they don't want to use MonoTouch? What are my options for developing and deploying an API built on MonoTouch? I know that I can use the --xcode option to generate XCode project files so that they can embed it into an ObjectiveC app, however, it seems that this isn't supported and may very be removed in a future release. The API I want to develop is actually meant to be cross platform. The fact that I want to use Mono basically boils down to developer preference (i.e working in C#, single code base). For the iOS version, I want to be able to use the MonoTouch libs. The only scenario I have come up with so far, and I don't know how feasible it is, is to develop the core in Mono (stock Mono, not MonoTouch), and embed that onto the target platform. Any platform specific features (like those provided by MonoTouch) would then need to be implemented natively for each platform. Regards, Vic -- View this message in context: http://monotouch.2284126.n4.nabble.com/Deployment-options-for-an-API-built-using-MonoTouch-tp4655613.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
