Monday, 26 March 2012

ASP.NET Web API Series

I am going to start working on a series on ASP.NET Web API covering the features.

Here is the list of the posts (I will update this list as I go along):

  1. Part 0: Why not WCF Web API
  2. Part 1: Getting started
  3. Part 2: Async basics and background 
  4. ASP.NET Web API Source code beta: Survival Guide
  5. Part 3: Async Deep Dive
  6. Part 4: Dependency Injection
  7. Part 5: MediaTypeFormatter explained
  8. Part 6: MessageHandler explained
  9. Part 7: Real-world message handlers
  10. Part 8: Message handlers on the client
  11. Part 9: MediaTypeFormatter on the Client
  12. Using the CachingHandler in ASP.NET Web API
  13. Introducing PocoHttp
  14. Introducing CacheCow: An HTTP caching framework for server and client
  15. Serialising request and response in ASP.NET Web API

3 comments:

  1. Hi Ali Kheyrollahi,
    Thank you this series of blogs are really good.

    I was reading doc about the new WEB API and also create my own web services using the HttpHandler. However I dont know what could be the best and solid approach for a good solution. I have the bad experience with Microsoft and LINQ that no everything which shine is gold. So what do you think about that?
    Thank you
    I read this article
    http://www.codeproject.com/Articles/112470/Developing-a-REST-Web-Service-using-C-A-walkthroug#_rating

    ReplyDelete
    Replies
    1. That is really old stuff. If you can use ASP.NET Web API then best is not to re-invent the wheel. Web API has taken care of so much and best sticking to it.

      Best is to start looking through the Microsoft sample here:
      http://code.msdn.microsoft.com/Contact-Manager-Web-API-0e8e373d

      This should give you an idea of how to do basic CRUD in Web API.

      Delete
    2. Thank you for your comment Ali Kheyrollahi I will look that website.

      Delete