Expose your Existing ASP.NET MVC Actions as JSON/XML API Endpoints
Why write separate actions to provide a JSON/XML API in ASP.NET MVC? If you are already using view models, MVC API Action Filter makes reusing your existing actions quick and clean.
Web and Game Developer
Why write separate actions to provide a JSON/XML API in ASP.NET MVC? If you are already using view models, MVC API Action Filter makes reusing your existing actions quick and clean.
In a previous post, we built a model-aware validator using Foolproof for ASP.NET MVC. Now, it’s time to create the client side version because posting back sucks.
MVC 3 gives us the ability to create model-aware validation attributes. What does this mean for Foolproof Validation?