This post by Jack Altiere describes how to build a REST API in .NET. This spurred a respose...
Firstly, I think really he is talking about a REST interface, not an API. REST is all about the interface. Maybe I am splitting hairs here, but I think it is important to be careful about terminology.
My main respoinse is this - use .NET 3.5 and the REST capabilities included as part of Windows Communication Foundation. I respect the enthusiasm in the blog post, but the thing is, most devs don't want just a REST interface. They want a service, and they want it to be accessible in various ways. REST is one of those ways. They want it to be easy to handle parameters. They want auditing and logging. They want an easy way to map URIs to methods. The .NET Framework v3.5, released in November 2007, gives developers those capabilities. Sure, you can roll your own REST Framework for .NET, but why would you?