Hmm, mono is a really curious thing to me. Maybe someone can explain this to me: Why doesn't MS commit to it?<p>One of the tenets of .NET was that it was to be platform-agnostic a la JVM but the story seems to be that they just didn't...get around...to implementing a Linux or Mac stack for various reasons (tight coupling to Win32 and existing COM servers, maybe?).<p>Now, Mono is reaching a state of extreme maturity. Why doesn't MS invest in this? It seems like their best way forward is dropping their single-vendor-stack mantra? Or perhaps they don't need to do so strategically yet -- once people <i>really</i> start demanding *nix and mac support they can "suddenly" change heart on mono?? This confuses me...but I'm not much of a strategist.
For a free and open source effort, check out <a href="https://github.com/koush/androidmono" rel="nofollow">https://github.com/koush/androidmono</a>. I just came across this and have not used it, but it looks promising.
I develop on a Mac using Mono and MonoDevelop. I just want to say I greatly appreciate all of the work that has gone into Mono and MonoDevelop. Thank you. :-)
Looks like there is no free version and the single developer license costs about 400$. That is going to be a big hurdle to get the casual indie developers interested.
So is the paid version the only way to go here? Since everything else in the Mono world is mostly free and open source I was hoping for the same with the mobile versions.
I've got yet another .NET shop, and have been meaning to break into mobile market(beside WP7, I know). Trying to weigh the benefits of going native (i.e. learning/hiring iOS/Java) vs using something like mono & present talent. Feedback would be greatly appreciated :)
ok, I've just run my first android app.
it took me about 1.5 hours to download/install everthing
Emulator is really slow, it took me ages first run in Debug mode and the UI response time is bad so far
<a href="http://flic.kr/p/9wsYQ8" rel="nofollow">http://flic.kr/p/9wsYQ8</a><p>so back to WP7?
There are few differences between Java and C#. There are even fewer differences between this and Android (java) development.<p>This Hello World is virtually identical to an Android hello world.<p><a href="http://mono-android.net/Tutorials/Hello_World" rel="nofollow">http://mono-android.net/Tutorials/Hello_World</a>
I read through the Architecture doc and it explains how they do it. However I cannot get an idea of how large the mono runtime on Android would be. Any ideas?<p>For small apps, the runtime could be the largest part of the app since the 'callable wrappers' are just proxying calls to the app.