Placefinder breaking about ngeo HOT 2 CLOSED

This is fixed as of commit 8ad391f, and version 1.7.1.0 has been pushed to nuget.

Unfortunately, could not find a good solution for this. The fix is a brute force implementation which required the creation of separate WebGet OperationContracts and new classes for Response2 and ResultSet2. These new DataContact classes compensate for the differences in the Yahoo JSON result format, depending on whether 1 or more than 1 results are returned.

Important

When a PlaceFinder request results in 2 or more reults, this will result in the placefinder service being invoked twice. The first try attempts to map a single result. If multiple results are returned, a second invocation is performed against a different DataContact target to compensate for Yahoo's inconsistent result format.

If they go and change it back to the old way, I will be a VERY sad panda........

from ngeo.

... and less than a day later, I am, a VERY sad panda! Thanks Yahoo!

from ngeo.