Tuesday, July 13, 2010

Droid Explorer 0.8.7.0

A new version of Droid Explorer was put up for download late last night. This version was initially just a maintenance release and consisted of more code refactoring. But it has since turned in to an actual release since some of the newly added features could be somewhat buggy.

One of the changes, code wise, is that all projects have been upgraded to Visual Studio 2010. Along with that, the WiX installer project now uses WiX 3.5.

I fixed the bug where files would no longer open on your system when double clicked. This may not have been an issue with all ROMs, but with CyanogenMod, it was. It seemed that 95% of the files on the system are marked as “Executable” in CyanogenMod now.

The biggest change is that you can now specify that you want to use an existing Android SDK, instead of having Droid Explorer download a trimmed down version of the SDK. This is really more for the advanced setup, and if you don’t have the SDK already setup, it is best you let Droid Explorer set it up for you.

Once you select that you want to use your existing SDK, during the install, you will be prompted for the path of the SDK. If the installer is unable to find the necessary components in the selected directory, you will be prompted with a message stating that it is not a valid SDK directory. Make sure you are selecting the root of your Android SDK.

Droid Explorer 0.8.7.0

A new version of Droid Explorer was put up for download late last night. This version was initially just a maintenance release and consisted of more code refactoring. But it has since turned in to an actual release since some of the newly added features could be somewhat buggy.

One of the changes, code wise, is that all projects have been upgraded to Visual Studio 2010. Along with that, the WiX installer project now uses WiX 3.5.

I fixed the bug where files would no longer open on your system when double clicked. This may not have been an issue with all ROMs, but with CyanogenMod, it was. It seemed that 95% of the files on the system are marked as “Executable” in CyanogenMod now.

The biggest change is that you can now specify that you want to use an existing Android SDK, instead of having Droid Explorer download a trimmed down version of the SDK. This is really more for the advanced setup, and if you don’t have the SDK already setup, it is best you let Droid Explorer set it up for you.

Once you select that you want to use your existing SDK, during the install, you will be prompted for the path of the SDK. If the installer is unable to find the necessary components in the selected directory, you will be prompted with a message stating that it is not a valid SDK directory. Make sure you are selecting the root of your Android SDK.