Thanks for feedback both to Wally and Nic. You have made valid points to go with MT/Xamarin first - and then if needed make the switch to Objective-C.
Even though this list has to be at least a bit biased taken into account that all subscribers has chosen the .Net approach I feel your arguments are very valid and honest - and some points I can use to backup my decision towards management. Thanks for taking your time to feedback. /Anders From: Wally McClure [mailto:[email protected]] Sent: 29. juni 2011 15:19 To: Anders Kjærgaard Hansen; [email protected] Subject: RE: [MonoTouch] Should I use MonoTouch, Xamarin or Objective-C for my next iPad project? My suggestion is fairly simple. Monotouch now, XamarinTouch once it is released. I expect Xamarin to keep their promise that XTouch will be compatible with MT, minus any changes caused by iOS 5 changes from Apple. This is the my current flightplan and is based on the issue that I am much more fluent in C#/.NET than on ObjectiveC and I have lots of sample code in MT. However, there is clearly risk involved in this approach. The XC/ObjC route clearly carries the least amount of risk, however, it also carries the longest timeframe assuming that you are not already proficient in XC/ObjC. Regarding timeframes, I can't speak to specifics(because I don't know), but Xamarin has promised to have a product out in 3 months. They are basically 1 month into this, so they are 2 months away, which would be the end of August. I'm sure that the Xamarin guys would be able to provide better details on timeframes and such. Anyway, that's my generalized thoughts. Hopefully, its helpful. Wally ________________________________ From: [email protected] To: [email protected] Date: Wed, 29 Jun 2011 09:01:55 +0200 Subject: [MonoTouch] Should I use MonoTouch, Xamarin or Objective-C for my next iPad project? Hi During all this talk about MonoTouch (MT) being more or less laid off, Xamarin only on its way, and IOS 5 launching in the fall, I am a bit unsure which technology I should base my next iPad app on. My current situation is that we have a full C# winforms application that has a pretty big Business Logic Layer and service interface with a webserver. I need to port this application to iPad as well. Since I have this large codebase in c# MT seemed an obvious choice. I would just need to create a new data and view layer. But, being unsure if MT will ever make it to IOS5, and unsure if current MT will be able to build to IOS5 (though some forum posts seems to indicate that it might will) I am not sure MT would be the right way. I probably need a prototype somewhere around september - so just wating for Xamarin doesn't seem valid either. Though development first will start in a month or so. So another thought I came up with is this: Is it possible to take a C#/.Net dll, use MT 2.4.2 to compile this to an Objective-C library that is then usable from an Xcode/Objective-C app? That way I might get best of both worlds as the state is right now. I will be able to reuse my c# logic, but not be dependent on MonoTouch or Xamarin to support IOS5 before my deadline. There might be better ways - and I am open for suggestions. Best regards /anders _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
