News for hackers. Stuff that matters.
Re:Android Ported to C# by acak on Tuesday May 01, 2012 @05:47PM (#3916529)
Forgive my ignorance. Which application lets you write native iOS apps in C#? Thanks.
Re:Android Ported to C# by untog on Tuesday May 01, 2012 @05:51PM (#3916541)
The guys who made this blog post make some software called MonoTouch.

http://xamarin.com/

It costs $400 for a license, though. But boy I am tempted... I know, I know- you need to go with the native languages for the best experience. But keeping a huge chunk of my codebase between platforms is a very, very interesting idea to me.

Re:Android Ported to C# by Fizzer on Tuesday May 01, 2012 @06:05PM (#3916585)
you need to go with the native languages for the best experience.

With MonoTouch, you still write against the native iOS UI. Therefore, from the user's perspective, your app is native.

Since the UI is the same, the only thing that could be different between an ObjC and MonoTouch app is performance. In my experience there's no noticeable performance hit with MonoTouch except for app startup time (my MonoTouch app takes about 2 seconds to startup on a 3gs)

Re:Android Ported to C# by bratsche on Tuesday May 01, 2012 @06:48PM (#3916707)
MonoTouch does give you a native experience. It's basically a C# binding for native APIs. It also has a few nice extras like MonoTouch.Dialog which provides a much nicer API for doing iPhone dialogs than using UITableView (although you can definitely use the UITableView API directly if you prefer).
Re:Android Ported to C# by fuzzythinker on Tuesday May 01, 2012 @08:35PM (#3917041)
I'll be great if they support F#, but seems like not, 0 answers from googling, except for this request: https://xamarin.uservoice.com/forums/144858-xamarin-suggesti...
Re:Android Ported to C# by migueldeicaza on Tuesday May 01, 2012 @09:54PM (#3917267)
F# on Android is doable, and on our list of things to do.

iOS is more challenging, since F# depends on some dynamic-ish features of .NET that are not currently supported by MonoTouch on iOS.

Re:Android Ported to C# by MichaelGG on Tuesday May 01, 2012 @11:45PM (#3917531)
I'm curious what F# features are you referring to? The generic hash/compare type functions?
Re:Android Ported to C# by malkia on Tuesday May 01, 2012 @11:58PM (#3917558)
Just guessing here, but code generation is not allowed on iOS.
Re:Android Ported to C# by alexrp on Wednesday May 02, 2012 @11:16AM (#3919479)
Right, which means we can't handle generic virtual methods, since we cannot JIT compile them. See: http://docs.xamarin.com/ios/about/limitations#Generic_Virtua...
Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @07:11PM (#3916772)
The thing holding me back is Monodevelop. It's even worse than Xcode.
Re:Android Ported to C# by ConstantineXVI on Tuesday May 01, 2012 @07:28PM (#3916817)
Kind of surprised we haven't seen JetBrains step up with a Mono IDE yet. They've already got the IDEA platform and ReSharper, combining the two seems a logical next step.
Re:Android Ported to C# by henrikschroder on Wednesday May 02, 2012 @06:20AM (#3918325)
Interesting! Going from VS 2005 to 2008 to 2010, Resharper has gone from must-have to nice to not needed anymore for me, since most of the features I relied on have been implemented natively in VS.

But MonoDevelop could sure use a lot of love...

Re:Android Ported to C# by mdaniel on Wednesday May 02, 2012 @01:57PM (#3920330)
I would bet they are bumping up against a developer bandwidth issue. Don't forget, they have about 6 commercial products, plus their own language now (and IDE, natch).

The good news is that the community edition of IJ is Open Source (Apache licensed, IIRC) and there are quite a few existing language editors built on top of it. It isn't a rich client platform à la Eclipse or NetBeans, but I doubt such a thing would be required to win the affections of those who are unhappy using MonoDevelop.

Re:Android Ported to C# by jbrechtel on Tuesday May 01, 2012 @06:45PM (#3916701)
"I know, I know- you need to go with the native languages for the best experience."

What about doing this improves the experience?

Re:Android Ported to C# by stouset on Tuesday May 01, 2012 @06:05PM (#3916582)
A very interesting idea to you, but one your users couldn't care less about.

Never forget about the users.

Re:Android Ported to C# by untog on Tuesday May 01, 2012 @06:08PM (#3916596)
It would be an interesting idea to them if they have an Android phone and I wouldn't have the time to code for two platforms otherwise.

I get that there is a tradeoff involved, but the Mono-x products are in an interesting space. They aren't webviews (like PhoneGap), they aren't a weird JS hybrid (like Titanium)- they're full native experiences. You'll get some newly released features later (I imagine), but the user experience really shouldn't be affected that much.

Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @07:12PM (#3916774)
The Mono guys have been very quick to support new iOS features so far.
Re:Android Ported to C# by josephcooney on Tuesday May 01, 2012 @06:15PM (#3916614)
How is this bad for 'the users'?
Re:Android Ported to C# by bryanl on Tuesday May 01, 2012 @06:54PM (#3916727)
People have responded with MonoTouch, but there is also Unity3d http://www.unity3d.com. You can author games for quite a few platforms with it.
Re:Android Ported to C# by moonchrome on Tuesday May 01, 2012 @06:59PM (#3916740)
Uses same VM - Mono, but has no bindings to native API's like monotouch/droid have
Re:Android Ported to C# by d503 on Tuesday May 01, 2012 @05:50PM (#3916536)
Re:Android Ported to C# by sambeau on Tuesday May 01, 2012 @07:30PM (#3916820)
Re:Android Ported to C# by philjohn on Tuesday May 01, 2012 @05:54PM (#3916554)
MonoTouch