Solved :-) You wont believe. Eclipse also could not connect to ADB, but successfully started it... The solution was I moved the adb.exe to its older SDK location: /tools. In the newer SDKs it is moved to /platform-tools subfolder.
Again: * All the 3 IDE successfully started adb from its new location: /platform-tools. * Also... I carefully checked the path environment var and /platform-tools was in it. * Even eclipse give a red misleading error message "Please ensure that adb is correctly located at 'C:\android-sdk-windows\platform-tools\adb.exe' and can be executed." and starts it. Note it states it requires adb.exe in the platform-tools. Then can not connect If you place adb in the /tools folder instead of /platform-tools all the 3 IDE successfully starts and connects to the adb. (ironically tools folder not even in my path) Thx for the tip to diagnose with Eclipse. Googling with Eclipse error messages solved the problem. That was my workday, progress zero :-( -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Deploy-problem-with-MonoDevelop-too-same-with-VS-2010-tp5624634p5625040.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
