Skip to content

Nick Riggs

Web and Game Developer

Month: August 2010

Expose your Existing ASP.NET MVC Actions as JSON/XML API Endpoints

Published on August 13, 2010

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.

Recent Posts

  • Expose your Existing ASP.NET MVC Actions as JSON/XML API Endpoints
  • Getting the id and name Attribute Generated by Typed Html Helpers
  • Client Side Model-Aware Validation
  • Render Your Model With Client Side jQuery Templates Instead of ASP.NET MVC Partial Views
  • Build Model-Aware Custom Validation Attributes in ASP.NET MVC 2

Recent Comments

  • http://www.newyorkcityburlesque.com/ on Foolproof Provides Contingent Data Annotation Validation for ASP.NET MVC 2
  • http://www.newyorkcityburlesque.com/ on Foolproof Provides Contingent Data Annotation Validation for ASP.NET MVC 2
  • auto insurance quotes, Twentynine Palms, CA on Getting the id and name Attribute Generated by Typed Html Helpers
  • auto insurance quotes Brentwood Tennessee on Simple AJAX Polling Plugin for jQuery
  • Shane on Entity Framwork’s Include Function Produces Inner Joins Instead of Outer Joins

Archives

  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • September 2009
  • August 2009
  • July 2009

Categories

  • API Action Filter
  • ASP.NET
  • Data Access
  • Foolproof
  • JavaScript

Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

© Nick Riggs. Powered by WordPress & Krusze Theme.