In the next few posts I am going to share my experiences creating a web application using Bing Maps and Hunch.com’s developer API. An additional step of deploying to as Windows Azure Web Site will be covered.
Source code has been published on GitHub.
The following lists technology used and/or required. Required bits in red.
- Visual Studio 2012 or Visual Studio Express 2012 for Web
- .Net 4.5
- Bing Maps Account
- Hunch Developer App
- Windows Azure Account
Concepts / Technology Covered
ASP.Net MVC Web API
I’ll be using ASP.Net MVC Web API to process Hunch.com API calls. This partly an excuse to get some practical experience using Web API, but it does serve a good purpose by hiding application account information from the end user.
Bing Map API
Hunch.com Developer’s API
I was searching for data exposed through and API to make something somewhat useful. I settled on Hunch. I started out thinking about a Twitter application, but Twitter has put up some hurdles to working with their data that make it not worth the effort to overcome.
I have been interested in Hunch since I read a Wired Magazine piece about the service’s co-founder. Hunch has an API that I was looking for. Using Hunch I could locate recommendations on a map, tailored to my tastes.
Publishing Windows Azure Web Site
The last bit is pretty optional, but I am publishing the web application as a Windows Azure web site. This part is simply to get practical experience using Azure services.
Everything in the Git repository is set to run the web application. Because the Web.config has some account information specific to the user/developer, I have excluded the Web.config normally found at the application’s root. Instead I included text file name Web.config.text. Rename the file Web.config and replace the account information with your own to use.
In the next blog post I’ll talk about setting up the Bing Map.