Mapping moving application from asp.net to wpf

Question

The company I work for has decided to create a wpf application with similar functionality to that of our website. One of the major components of the website is the use of the MapQuest javascript api. I have been tasked with working on an alternative that would work for the wpf application.

I have done plenty of research and I have mocked up a WebBrowser control that holds an html page where the map can be built. Unfortunately we use much more than just a map though, there are polygon geofences, points, directions, etc… This requires (in the asp.net side) a lot of client side script to handle all of this. From what I have seen with wpf and a WebBrowser control – another layer of complexity is added to manage all of that client scripting.

My question is –

Do I continue down this path of creating a WebBrowser control? Or.. Should I look at third party libraries such as GMap.NET?

**One side note. MapQuest is the only option that I have, as we pay licensing to use it.

Answer 1

Found the solution... well, not really a solution to the problem but... Company decided to go the route of the bing map api for wpf. Going the other route with the MapQuest javascript api inside of a WebBrowser would have been a total nightmare to maintain.