I just posted a new version of the control, which addresses some concerns from existing users about deserializing the geocoding responses returned from Google's servers. While Google's documentation stipulates the response as being in one format, the responses vary wildly. Now the deserialization checks for format before deserializing. This should solve the problems that have been reported.
Another nice thing that has made it into the geocoding and reverse geocoding features are language. User Sjeff contributed a language selection for reverse geocoding. Thanks for that. Now geocode and reverse geocode methods methods have overloads that allow you to pass a CultureInfo parameter and get the response back in that language (if Google supports that language).
On top of handling this user feedback, I added a nice feature that let's you focus on your users. The GoogleMap class now has a property called CenterOnUserLocation. By default it is set to false. But if you set it to true the map will center on the user's location. The location is based on the IP location, so it is not an exact location.
It gets set as part of the map initialization, so if you handle the MapLoaded event you will be able to see where your users are.
In the spirit of disclosure, the IP location service sends a request to this website in order to improve the quality of the IP location response. No personal information is gathered, nor is any information about the hosting website gathered. This is purely done as a service to provide better IP location information.