Best Practices for API Versioning

See more:

WCF

webservice

versioning

Hi,

I'm looking for advice on web service API versioning.

Until now we've used cache manifest web apps and web services to provide offline web functionality.

This meant that we could be confident that the user would get the latest version of the software for the current API and therefore we only had to manage a single instance of the web service.

We've now moved into the various app stores and we're no longer going to have this type of control and are going to have to manage multiple versions of the web service.

I'm looking for advice on any products in the market place which could aid this type of implementation?

My current strategy is to have multiple application roots, one for each version. I.e.

http://mydomain/myapi/v1.0
http://mydomain/myapi/v1.1
http://mydomain/myapi/v2.0

Are there any better strategies than this?