| I honestly have no idea what point you're trying to make. The problem is that it's hard to understand what does what and how it does it. Things in even the same project behave differently. They introduce massive architectural changes and then abandon them. Searching for something in SO now is a crap shoot, which slightly in correct answer will you get because the asp.net team changed their mind again? And you can have all these things running in one project, all acting differently. I work with clients on MVC 3,4,5, with parts in web API 1 and 2 and parts in odata. And they all behave differently. For example, and this is just one of many, a JSON date from an MVC controller is 'Date(173737273)', from a web API it's '2016-12-26 23:00:00.0000', from an OData controller it's '2016-12-26 23:00:00.0000Z'. That Z changes behaviour btw and makes the terrible assumption your date is in the same TZ as your server. All of them are parsed different and will return different dates in javascript. |