>I see three recommendations to switch to WebApi - we can't all be wrong :-}
>
>One suggestion - go for the newer 'Attribute Routing' - it's far more flexible and REST friendly than the older convention based approach.
>
>
http://www.asp.net/web-api/overview/web-api-routing-and-actions/attribute-routing-in-web-api-2Go on, just throw in more stuff for me to understand, why don't you? :)
I've got a Web Api example to work! Had to get VS 2013 and update to Web Api 2 to get it to work, but it looks like it works properly, so now I need to see if I can do this to use the business objects I created or if I'll need to create Models and controllers to pull my data out of the database (and post it back after being edited).
