4 ms·
Having spent the better part of 3 years creating REST services with .NET, I strongly recommend you do NOT use traditional WCF. The WCF Web API stuff looks inte
by dos1 15y ago
Having spent the better part of 3 years creating REST services with .NET, I strongly recommend you do NOT use traditional WCF. The WCF Web API stuff looks interesting but still seems immature. I've found ASP.NET MVC to be the best tool for creating REST apis.
- chrislomax 15y agoThanks for the advice I have found the routing in MVC and their returns types (JSON etc) working really well to be honest, I will take a look at that Thanks
- hkarthik 15y agoEven MVC is a little heavy and you don't get a lot of things for free with it. Compare it to some of the Java OSS projects like Enunciate and it still requires a lot of extra work. On the .NET side, I would suggest looking at Demis Ballot's excellent Service Stack library. http://www.servicestack.net/ http://www.servicestack.net/