Those who have been following Project Watch will know that I have been leading the development in a large database project using SQL Server 2008, Windows 2008 and Visual Studio 2008. Relatively heavy stuff. Part of that project, though, involves the creation of a mashup that displays our spatial data on a map - yes, I know, all …
So after choosing microsoft for everything why....
did I choose a Microsoft mapping service?
a) Because I'm a rebel
b) Because I wont try anything outside the MS stack on the project
You chose Microsoft because you develop on a very limited stack. This means you limit the problems you have to that of one company.
Apart from the obvious eggs in one basket, the money and the proprietary nature of the software I can understand your simple approach. Its enough of a challenge developing with bleeding edge software.
MS Maps are however, uglier than the Google counterparts.
(btw. I note that you skipped the excellent Yahoo maps?)
We have been using Virtual Earth for the last year or so and we are very happy with the results. I have to say that our main reason for going with Microsoft was the licensing, Google were not easy to deal with on this and seemed to have a ridiculous licensing cost (i'm sure that with more effort we could have found a solution but why bother?) whereas the MS licensing was easy to deal with and, for us at least, was a good pricing structure.
- Xmas Round-up Ten top tech toys to interface with a techie’s Christmas stocking
- Google embiggens its fat vid pipe Chromecast with TEN new supported apps
- Microsoft: Don't listen to 4chan ... especially the bit about bricking Xbox Ones
- Shivering boffins nail Earth's coldest spot
- Thought your Android phone was locked? THINK AGAIN