Mono For Android 1.0.2
Mono for Android 1.0.21515 is the first release done by Xamarin.
Visual Studio Users: Download monoandroid-1.0.2.msi and install.
MonoDevelop Users: You should be prompted to upgrade next time you open MonoDevelop, or you can use Help->Check for Updates.
The System.Data.Services.Client.dll assembly is now included.
System.IO.IsolatedStorage is now available, making it easier to share code with Windows Phone 7.
The runtime (including GC) was rebuilt, and includes a number of GC fixes. Hopefully this will resolve some of the outstanding GC issues, though it does not resolve all outstanding GC issues such as TouchTest.
The installer will actually work on Mac OS X Lion.
When installing on Mac OS X Lion, we now prompt to install Java if Java hasn't already been installed.
On Windows, if activation fails then a MfaActivation.dat file will be created within the Documents folder. You will be able to email us this file so that we can return a license file for activation if you're unable to activate online (e.g. behind corporate firewall, etc.). See the Offline Activation page for more information.
Version 2.6.5 of the Mono for Android Addin has been released. This release includes debugging and stability fixes, and we recommend all users update to this version via the Add-in Manager.
- 690406: Additional int->enumeration conversions.
- 13: When deploying my first simple app to the emulator, I get an Unhandled Exception
- 33: mandroid generates a Java method override for members that match by name, but aren't actually overrides.
- 102: mandroid doesn't properly capture javac error messages.
- Custom attributes and AndroidManifest.xml can now contain "properly cased" resource references; they will be lowercased by mandroid in the resulting AndroidManifest.xml (as required by Android).
- Initialize Runtime.init() arguments separately within MonoPackageManager.java. (This file is generated at build time, and is placed at e.g.obj\Debug\android\src\mono\MonoPackageManager.java.) This will hopefully narrow down (but not fix) some reported issues with ajava.lang.NullPointerException within the Runtime.init() call on some devices.
Warning: Samsung shipped a broken kernel with Android 2.1, which is not able to support JIT compilation. If you possess a Galaxy-class device with Android 2.1, you will get unexpected results, this is caused by a kernel bug that breaks cache coherency, rendering any engine doing JIT compilation useless. Check with your manufacturer/carrier for an Android 2.2 update.