Error - This version of ADT requires Android SDK Tool in revision or above

This version of ADT requires Android SDK Tool in revision <17> or above
Current version is 8
Please update your SDK tools

If you get above error even after installing latest SDK, quite possible you are not pointing to the right SDK in eclipse

Follow these steps

• Open Eclipse
• Select menu Window->Preference
• Select tab "Android"
• Select the "SDK location" to the folder where you installed the SDK .. quite possibily c:\program files\Android\android-sdk

Android development - setup DEV environment

 Note this is work in progress and I am just writing down things to maintain the list of items I had to setup for starting up development on Android.

What you need

• Eclipse (classic recommended)
• Android SDK
• Andriod development tools plugin for eclipse (ADT). In some cases, a new revision of ADT will have a dependency on a specific revision of the Android SDK Tools. If such dependencies exist, you will need to update the SDK Tools package of the SDK after installing the new revision of ADT. To update the SDK Tools package, use the Android SDK Manager (explained below)

Step 1. Preparing Your Development Computer

• First download Eclipse  - classic is recommended)
• http://www.eclipse.org/downloads/
• Unzip the downloaded zip folder into a folder where you want to run eclipse from. There is no installation for eclipse

Step 2. Downloading the SDK Starter Package

• Download the Android SDK from http://developer.android.com/sdk/index.html (installer_r18 ....exe)
• Install the downloaded file
• Run Android SDK manager (SDK manager.exe from where you installed SDK)
• Launching the Android SDK Manager - The Android SDK Manager is the tool that you use to install and upgrade SDK packages in your development environment. You can launch the Android SDK Manager in one of the following ways.

• If you are developing in Eclipse and have already installed the ADT Plugin, follow these steps to access the Android SDK Manager tool:
• Open Eclipse
• Select Window > Android SDK Manager.
• Launching from the SDK Manager script (Windows only)

For Windows only, the SDK includes a script that invokes the Android SDK Manager. To launch the tool using the script, double-click SDK Manager.exe at the root of the the SDK directory
Setup proxy in Tools -> Options (popup to enter user name and password will come later). Close the ADK manager and open again for it to refresh the tools required

The list will be shown what needs to be downloaded. You could choose extras if you need them. The latest version of Android will be selected by default
Click on "Install <number> packages" button

Step 3: Configuring Eclipse for Plugin

• Open Eclipse
• If proxy, then select menu Window -> preference
• Select General -> Network connections
• Select active provider = Manual
• Edit http and https options by selecting one at a time and clicking on edit
• Enter proxy settings and save
• Select menu Help -> Install new software
• Click on Add and enter https://dl-ssl.google.com/android/eclipse/ in URL

Enable windows authentication (IIS) on a Windows 2008 server

Recently, I had to setup an old VS 2005 application on a windows 2008 server. I did everything right and setup the virtual directory for the web site. But when I tried to run the web site in VS, the site would not open up. I found that this was because the virtual directory was not set to accept windows authentication.

In IIS 6, it was pretty straight forward - go to security tab in IIS and edit and enable. But here I was not able to see that option for the virtual directory. All I could see were the options anonymous access, forms authentication and asp.net impersonation.

Long story short, you have to enable that as a feature on a 2008 server.

To do that

• open control panel and click on "add or remove windows feature"
• Expand the node - roles->Web server (IIS)
• right click on web server node and select "Add role services"
• in the new window that opens up, on the right side, under "role services", select checkbox "security->windows authentication
• Under "management tools", option, select checkbox "IIS 6 management compatibility"
• Click on Next and then Install
• restart server
• go back to IIS and the virtual directory and check the "IIS authentications" available and you should see "windows authentication" as the new option