It's a common misconception that Web API is built on or tied to MVC. It's not though. You can use it in a WebForms site just as easily as in an MVC site. You can even self-host Web API outside of IIS entirely.
Also, Web API isn't intended to replace WCF. The "connected systems" people have a whole different set of needs than people building simple web-facing APIs. I don't think we should expect to see WCF or "Add Service Reference" going away anytime soon.
I had totally forgotten about that, although I have seen WebForms used in an MVC site as well.
I did NOT intend to imply that it was a replacement for WCF. I meant to imply that it is a replacement for the WCF REST Starter Kit, and if MS didn't make a huge deal out of it, a lot of people that had gotten used to using WCF for web services would never see it.
Comments
It's a common misconception that Web API is built on or tied to MVC. It's not though. You can use it in a WebForms site just as easily as in an MVC site. You can even self-host Web API outside of IIS entirely.
Also, Web API isn't intended to replace WCF. The "connected systems" people have a whole different set of needs than people building simple web-facing APIs. I don't think we should expect to see WCF or "Add Service Reference" going away anytime soon.
I had totally forgotten about that, although I have seen WebForms used in an MVC site as well.
I did NOT intend to imply that it was a replacement for WCF. I meant to imply that it is a replacement for the WCF REST Starter Kit, and if MS didn't make a huge deal out of it, a lot of people that had gotten used to using WCF for web services would never see it.