Hi! I wanted to know too! So this is what I did...)
Browse to Oracle and downloaded the following JDK 7 for 64-bit systems. - you may also want to change this if you are on a 32-bit system by making the right selection for the system you are working with - http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html jdk-7-windows-x64.exe<http://download.oracle.com/otn-pub/java/jdk/7/jdk-7-windows-x64.exe> First I start off with the common X64 problem and it should be known that it is generally a good idea to have the 32-bit version available if required to switch using PATH and environment variables. Before I began with the X64 edition of Java 7, this is what my Java version looked like; *C:\>java -version* *java version "1.6.0_25"* Java(TM) SE Runtime Environment (build 1.6.0_25-b06) *Java HotSpot(TM) 64-Bit Server* VM (build 20.0-b11, mixed mode) Nothing out of the normal, Eclipse is building Android APK files natively and Visual Studio 2010 is working. Let's upgrade... Using an - Administrator: Command prompt and the JDK moved to the C:\ I type the following; *C:\>jdk-7-windows-x64.exe* * * Launching the Oracle Java(TM) SE Development Kit 7 (64-bit) setup and I select to install everything, including the demo's as a Custom Set-up, leaving the default install path set to - *C:\Program Files\Java\jdk1.7.0\* After a short while, I'm prompted with the following path for the JRE set-up and again leave it default. *C:\Program Files\Java\jre7\* 3 billion devices run Java, nice installer and set-up program I'm looking at here.. hm hm hm.. now! *C:\>java -version* *java version "1.7.0"* *Java(TM) SE Runtime Environment (build 1.7.0-b147)* *Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)* Looking good! :-) So now.. going back a step and downloading the installer I'm in for a treat! Step 1 - Install the Java JDK Download and install the *Java 1.6 (Java 6) JDK*. The JRE is not sufficient. The Android SDK requires the*32 bit* *JDK*, that is, select "* Windows*" for your platform, not "Windows x64". OK... we all know that you SHOULD NOT... does not mean me, that is for someone else right? So I hop over to Xamarian and download the installer from - http://android.xamarin.com/DownloadTrial They are happy that was a real email address :-) - Cool! I've got the installer and I'm ready to put this to the test... I move this MSI installer into the root of my C:\ drive and from a command prompt running with administrative rights; *C:\>monoandroid-1.0.1.10323.msi* * * I select both options during install and allow 1.0.1.10323 to complete installation of the Android and Visual Studio 2010 plugin. When Visual Studio 2010 launches, I create a new MonoAndroidApplication with C# and click build, which compiles correctly. Clicking the green > DEBUG arrow (opposed to hitting F5) I fgets System.IO.FileNotFoundException with the path for ADB. A bit of reading between the lines and sure enough I should be able to get this working, after all PATH's are easy with such detailed information, just make sure the ADB executable is where it's looking right? Taking a look at the path - *C:\AndroidSDK\android-sdk-windows* The MONO debugger is looking for - * C:\android-sdk-windows-platform-tools\adb.exe* * * So I copy a few files to that expected location and reset our path environment variables.. This results in a System.ComponentModel.Win32Exception and a prompt to get an activation number and buy a licence... Professional ($399.00) For individuals and micro-ISVs. Distribute your apps on the Android Market and other public marketplaces. Includes a one-year subscription to product updates. Sure looks like it has every possibility of working and making great apps, even though it is advised to use a 32-bit system.. To test how this works with Eclipse, I open and create a new project with MOTODEV Studio for Android 2.2.0, give it a name and target Android 2.1-update1. [2011-07-31 15:55:22 - xama] ------------------------------ [2011-07-31 15:55:22 - xama] Android Launch! [2011-07-31 15:55:22 - xama] adb is running normally. [2011-07-31 15:55:22 - xama] Performing com.xama.MainActivity activity launch [2011-07-31 15:55:22 - xama] Automatic Target Mode: launching new emulator with compatible AVD 'Test1' [2011-07-31 15:55:22 - xama] Launching a new emulator with Virtual Device 'Test1' [2011-07-31 15:55:26 - xama] New emulator found: emulator-5554 [2011-07-31 15:55:26 - xama] Waiting for HOME ('android.process.acore') to be launched... [2011-07-31 15:57:03 - xama] HOME is up on device 'emulator-5554' [2011-07-31 15:57:03 - xama] Uploading xama.apk onto device 'emulator-5554' [2011-07-31 15:57:03 - xama] Installing xama.apk... [2011-07-31 15:57:05 - xama] Success! [2011-07-31 15:57:05 - xama] Starting activity com.xama.MainActivity on device emulator-5554 [2011-07-31 15:57:07 - xama] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.xama/.MainActivity } [2011-07-31 15:57:08 - xama] Attempting to connect debugger to 'com.xama' on port 8612 That went well! Glen * * On Sun, Jul 31, 2011 at 1:02 PM, Wally McClure < theevilprogram...@hotmail.com> wrote: > > ------------------------------ > From: theevilprogram...@hotmail.com > To: monodr...@lists.simian.com > Subject: Java 7 > Date: Sat, 30 Jul 2011 23:01:23 -0400 > > If I understand things correctly, there's a new version of java. I dont > know that much, so i'm just going on what i hear. Does anyone know if it > works with the mono for android? > > Wally > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > > -- Glen Hassell Inner Technique http://innertech.com.au/ Office: 03 9687 0006 Mobile: +61 (0) 438 340 385
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
