I have also made a change to a few of the methods available from the service so I have placed below a message sent to all API developers over this weekend. My boss also saw the message and declared that the way I have authored it as 'a roller coaster ride', since I am write it as 'good-point then bad-point then good-point', and so on.! Oh well, this ride is fun, but you must hold on....
These now have an additional parameter added to the end of the list of parameters:
Secondly, the Tesco API is now running in Azure, the Microsoft cloud computing service. This means I can offer a far more scalable API than on my single server solution.
1) Configure/Update your service endpoint pointing to lansley.com to ensure it has the latest configuration (including the 'breaking change' above).
2) Open up your text find/replace facility in your IDE (in Visual Studio 2008 just press CTRL-H).
3) In the 'find' box enter the lansley.com end-point: http://www.lansley.com/TescoAPI/TescoAPI.svc
4) In the 'replace' box enter the Azure end-point: http://tesco.cloudapp.net/TescoAPI.svc
5) Ensure you have the 'replace all' scope set to 'everything in this project'.
6) Hit 'Replace All' (in VS 2008 client apps, I have found the 'replace' occurs more than 40 times).
7) Compile and test.
Unfortunately whenever I announce a new function or a 'breaking change' you will have to switch the service end-point back to lansley.com and then 'find and replace' back to Azure again. Microsoft are sorting out a fix and one day the problem will go away.
In the meantime, using the API on Azure means I can finish coding and testing a great new 'accelerator' for Internet Explorer 8 that will allow people to highlight food names on any web site and search for them at Tesco.com. They won't know but you will know the accelerator is using the Tesco API to work. You see? Code an API once and find a million uses!