Here is the list of the posts (I will update this list as I go along):
- Part 0: Why not WCF Web API
- Part 1: Getting started
- Part 2: Async basics and background
- ASP.NET Web API Source code beta: Survival Guide
- Part 3: Async Deep Dive
- Part 4: Dependency Injection
- Part 5: MediaTypeFormatter explained
- Part 6: MessageHandler explained
- Part 7: Real-world message handlers
- Part 8: Message handlers on the client
- Part 9: MediaTypeFormatter on the Client
- Using the CachingHandler in ASP.NET Web API
- Introducing PocoHttp
- Introducing CacheCow: An HTTP caching framework for server and client
- Serialising request and response in ASP.NET Web API
Hi Ali Kheyrollahi,
ReplyDeleteThank 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
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.
DeleteBest 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.
Thank you for your comment Ali Kheyrollahi I will look that website.
Delete