Friday 15 May 2015

c# - Web API 2.2 and OData V4 Route Conventions -



c# - Web API 2.2 and OData V4 Route Conventions -

i upgraded odata v4 , realised routing conventions have changed. instead of

http://somesite.com/api/products/1

you have following

http://somesite.com/api/products(1)

now fine new apps going forward, need back upwards traditional url's legacy apps. there way back upwards both url's, or traditional url time being?

if have next example

[odataroute("{key}")] public async task<ihttpactionresult> put([fromodatauri] string key, dealer dealer) { // logic code here }

i next error

the path template '{key}' on action 'put' in controller 'dealers' not valid odata path template. resource not found segment '{key}'

if switching odata v4 before version, there several breaking changes.. i.e. example, v3 clients not able consume response returned v4 service... hence uri may to the lowest degree of problems..

if need back upwards existing clients.. alternative host 2 versions of same service.

c# asp.net-web-api odata

No comments:

Post a Comment