Visual Studio 2015, Update 3.
Create a blank solution. Choose Add New Project -> Visual F# -> Android.
Create either a Blank App (Android) or a Unit Test App (Android).
The app is created successfully.
Right click on References, and choose "Add Reference". The following dialog box pops up:
Note that when you look at the Project Properties, there are two "Application" tabs. The second one generates an error:
Once the project has been unloaded, it can no longer be reloaded. The resulting error message is:
I have reported this on the Xamarin Forums, but the process is slow. I'd like to find a workaround, but I'm fumbling in the dark. Once I've unloaded the fsproj file, I can't find any mention of "frameworkName", and I can't reload it either.
My Android settings appear to all be up to date:
Does anyone know of any workarounds that will allow me to start unit testing my existing app?
I believe I have a fix for this issue :)
Xamarin expects F# 3.x to be present, which at this point must be manually added. You should be able to download F# 3.x here
Please let me know if this fixes the issue for you.
Thanks!
Edit: I have filed the following bug as well: https://bugzilla.xamarin.com/show_bug.cgi?id=42970
I am new in developing apps for Android with Java Eclipse.
I get a simple problem: after following the procedure explained here:
http://www.tutorialspoint.com/android/android_hello_world_example.htm
I tried to push the "Finish" button to create my first app, but it doesn't work: the wizard remains open and nothing happens.
Also, I have several problems in the Demo apps, errors like:
'<>' source operator is not allowed for source level
and many more.
I guess I created problems with the configurations.
Thanks if you can help me to create my first app for Android and to load
the demos.
It is really had to tell what is the problem, but as Abdullah advised to use android studio because it is well designed to develop android applications. and most of the company's now days use android studio as there IDE preference, but still its developer's choice. Eclipse ADT plugin is buggy
I am a android beginner. I am going through the book listed in the title. I haven't even made it past the first chapter without running into problems. I have installed the latest version of Eclipse. However, the examples shown in the book are not much like my version. For instance, this main.xml file that's supposed to be in the layout folder is not there. The "New Android Project" dialog box is arranged very differently and the package explorer is called project explorer. Is there a way to get this kind of eclipse in the book? Or do I just have to interpret it best I can? Any help would be much appreciated! This question has been down voted and closed by another user. Could someone please tell me why? I am just trying to get some help.
As different Android APIs(ICS, JB, etc.) are released, they sometimes change the ADT (Android Development Tools) for Eclipse. The ADT is plugin for Eclipse. This plugin is what gives you all those neat buttons in the toolbar and the XML layout interaction.
The book you are reading was designed for Android 4.0(Ice Cream Sandwhich). As of right now, Google has released up to Android 4.2.2(JB 4.2). There has been some significant changes to the ADT going from ICS to JB, but in my opinion, they are for the good. Lots of really neat and new features. Here is a Google resource explaining the different API releases for Android: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels
I would say continue reading the book as it will teachs you the basics of Android, but when you want to do some in depth coding, that book isn't going to be very useful and you may have to do a little research online. Reason is, Google releases at least two new versions of Android every year. Every version changes, and adds new features. In other words, the book you are reading is already out of date. Android OS development moves way to fast for authors to keep updating their books.
To answer your question, your probably going to have to interpret it the best you can since, most likely, by June/July, Key Lime Pie is going to out, and the ADT your using NOW will be outdated. You should really learn the fundamentals of Android OS and how it works in the background and how processes things. After that, everything else should be easier to learn.
An alternative to the book you are reading is this: http://developer.android.com/training/basics/firstapp/index.html. This is straight from Google and is constantly updated and tweeked. This will be the most updated and useful information on how to write Android apps.
Hope that helps!
few days ago, when I was debugging an Android project under eclipse I've found some great functionality: "All instances..." and "Instance count". I wanted to share my findings with rest of my colleagues, but none of them had this functionality in their eclipse install (we all use eclipse 3.7).
What's even more weird now I'm also missing this functionality.
As far as I can tell this functionality is build within eclipse from version 3.3 and available to projects using Java 1.6 and above as mentioned here and here (we're using 1.6).
See bottom of this link to see what functionality I'm talking about. It even has it's own shortcut in options (ctrl+shift+n) so I think there must be a way to use it again.
I was looking for it while debugging and while the debugger was in "stopped" state.
Anyone can help me put eclipse in right view/perspective/state to see this functionality again?
EDIT
Here is the documentation entry from eclipse help page: link
Thanks for any suggestions,
kajman
After some more digging I came to following conclusion:
DalvikVM does not support "instance retrieval".
On eclipse help page mentioned in EDIT section it written:
This command is only available if the Java virtual machine you are currently using supports instance retrieval.
Maybe there is an option to enable this option in DalvikVM, but I doubt it unfortunately.
Also when debugging on phone "Drop to frame" functionality is missing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have been using Eclipse for Android development and don't have a problem with it (I also use it for Web Service and C++ development under Linux) but I want to give IntelliJ IDEA a go as it appears to have favourable reviews. This is easily possibly now that IDEA 10 has been released with Android support enabled in the Community Edition.
I have looked at IDEA and it looks pretty good to me with the only downside being the lack of UI on .xml file editing (AndroidManifest.xml for example) and the user interface builder provided with ADT 9.0.
Has anyone got experience they can share on IntelliJ IDEA and Android development?
EDIT: Thanks all; I'm sticking with Eclipse as I know it pretty well and it allows me to do pretty much anything (Java-related) I like for free. I shouldn't look a gift horse in the mouth!
The only benefit for me: You code as fast as formula 1 :). Really. If you're used to Resharper in .NET programming, then you will code as fast as in .NET. Even faster.
Bad thing: lack of some Eclipse's tools (browse my questions for details) and it seems that Eclipse's compiler--which you can use from IntelliJ as well--is better. Because of the lack of some tools you are forced to use many 3rd party tools.
The bottom line is: if you don't have problems with Eclipse, then stick to it. I hated Eclipse's slowness and that's why I moved to IntelliJ.
EDIT 23 Jan 2013
IntelliJ has improved a lot. They now have UI visual editor, a great connection to Android SDK and at this moment I can't really think of any feature which Eclipse has and IDEA does not have. What's better, I will say again that IDEA has more features than Eclipse.
EDIT 11 Mar 2014
Again IntelliJ improved. With its visual UI editor for XML layouts and itself being used as the base for Google's Android Studio, its still the best IDE around.
The only flaws for Android developer are IMHO:
it still does not perfectly import dependencies (libraries) so you have to fix things manually
it does not perfectly recognizes other projects (modules) which sometimes you have to add those modules manually
a support for Google Glass does not exist
All this is referring to when importing projects made in Eclipse, which happens very often to anyone working on multiple Android projects.
I have used both, they aren't that different. A lot of it is just what you are used to. Personally, if you aren't having any problems with Eclipse, I would not suggest switching. There are no advantages that are worth the learning curve.
I switched to IDEA for my android development.
Intellisense actually works
IDEA is much faster
The refactoring is nicely done, and the "inspections" catch a lot of places where refactoring would make sense
Things I miss:
The new Layout viewer from Android 3.0. I always modify the layout xml, but it's nice to be able to switch over and get an idea of what it will look like without running the app. I do load up eclipse for this reason when I do heavy layout editing.
Hover documentation. In intelliJ, you have to press ctrl+Q to get the javaDoc of an existing method call (vs intellisense popping up as you code).
I know eclipse is free, but come on, I don’t know how people actually use it to build software. I like open source as much as the next guy, I just like “high quality open source” which may be an oxymoron.
I want to get work done and not fight the tool no matter how free it is.
After 2 years of Android Development on Eclipse I finally give up. I hate it because:
1. Eclipse is slow.
2. Search and autocomplete is poor.
3. Require big among of memory.
4. Crashing and hanging constantly.
5. Correct or incorrect way of closing Eclipse may cause workspace and settings crash.
Eclipse: reminding me every time I use why I normally don't use it. -
Romain Guy
You can check some of interesting IntelliJ IDEA features here
Google has introduced new intellij-based IDE for android development (if you dont want to pay for intellij), you can find more info here http://developer.android.com/sdk/installing/studio.html
I am interested in this question too. For me, eclipse starts to be slow as more plugins installed: CDT, aptana, pydev, ADT....
IDEA seems like a light-weighted and interesting alternative. For the lacking of layout xml editing, you may do it with http://www.droiddraw.org/, or its desktop version. Pretty amazingly easy after reading the droiddraw tutorials.
I haven't got enough experience with IDEA, so cannot help a lot. Hope more people cast light on this issue.
Thanks,
Frank
I think Eclipse has all the features that an IDE should have these days.
But from my point of view it does everything on the wrong way (I am a Visual Studio fan).
After I tried IDEA, I had to realize that it can be customized to act nearly the same as VS, so it IS a very good IDE.
And the version 12 has UI editor for Android.
I can say that try to compare their IntelliSense (or whatever you call it), the debugger (including watches) and the editor. Much more better, smarter, faster for a daily use.
IDEA ultimate is not free, but if you would like to make money with programming I think you can make it easier with professional tools.
I would never pay for Eclipse.
As a new IDEA user I found the IDE to be somewhat overwhelming at first. The IDE contains more options than I thought possible and can bring into question - "Just how many checkboxes can you fit on a screen". Once the shock passed and I was able to complete a small project, I'm in love. Sorry Eclipse, but you were kind of flakey and would have unpredictable behavior. IDEA is rock solid.
As a programmer I want rock solid tools and sometimes the phrase "you get what you pay for" is valid.
Google's Android Studio is built on top of IDEA, assuming that it will be the "Official" developer tool when it reaches 1.0, it might be worth getting up to speed by learning IDEA.
It also has a "dark" theme built in so you don't have to mess around with Eclipse plugins.
Quick comparison
between eclipse 4.3.2 and intellij 13.0.2:
I will refer to intellij idea as I as an abbreviation below (e.g. I12 means intellij idea version 12)
Both are fine .
Pro Intellij are:
Faster compiler mode:(introduced in I12) exactly as with eclipse, now Intellij compiles everything continuously in the background and shows you files that doesn't compile with red zigzag. Exactly as Eclipse but less heavier and more responsive .
Android UI editor: (introduced in I11) even better than the one in eclipse ADT plugin: it shows more properties as android:layout_span ,i.e. Advanced properties that are hidden in Eclipse UI editor forcing you to edit them from Layout XML , can be easily editted from Intellij UI editor. Also while Eclipse UI editor hangs when selecting multiple components then editting one common property , this is extremely fast and easy in Intellij UI editor. It also can show you a preview while editing XML code, which you can't do in eclipse.
Best content assist : it auto completes when you enter next limiter (space or semicolon or brackets or dot ) you don't have to press enter then press the next limiter, exactly as Visual Studio Intellisense. Also Intellij puts most relevant result on top. another feature introduced in I12 is that it searches if matches are available from the middle not from start.
Fast: intellij is much faster than Eclipse. Eclipse 3.8 is slow and Eclipse 4.2 is even slower due some bugs, that were fixed gradually in Eclipse 4.2.1 and 4.2.2 releases .
more stable than eclipse. In Eclipse, A row of Layout properties editor may stick on screen while you scroll, a very bad UI glitch. Also Eclipse x64 crashes very frequently as compared with eclipse x86 or Intellij, may be because of bugs in JDK x64.
Add framework support:( New in I13) a wizard to add framework support
As of intellij 13, it has wizard like (New->Android-> Android Activity) as that in eclipse adt plugin , maybe the only difference is the intellij wizard may force you to a higher minimum SDK version, while eclipse doesn't .
Con Intellij:
Gradle: Android project wizard: (New in I13) when you create an app you can define in a gui wizerd : min sdk , target sdk , icons and theme (all these fills in the gap between eclipse and previous Is) and support mode ( an advantage over eclipse). Although this might be considered an advantage, gradle added so many errors to managing an android project, that intellij became not usable as before in intellij 12. most errors require either changing configuration and updating a maven repo from internet , or navigating to a folder and running a command from terminal.
Doesn't support NDK (Native Development Kit for development in C/C++)
I have been using IDEA for professional Android development for almost a year, it is much better than Eclipse because:
The IDE is much faster and stable
Excellent interface designer
Other good enhancements such color picker in XML, creating resource directories and creating String resources.
IDEA is much better for Android development and you will increase your productivity for sure, Google knows this, that is why Android Studio is built on top of IDEA