<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Vahid Taslimi's Web log (وبلاگ وحید تسلیمی) - WCF</title><link>http://old.taslimi.me:80/Tags/WCF</link><description>Vahid Taslimi's Web log (وبلاگ وحید تسلیمی) - WCF</description><item><title>ASP.Net WEB API VS WCF Service</title><link>http://old.taslimi.me:80/asp.net-web-api-vs-wcf-service</link><description>&lt;p&gt;Well as soon as i heard and read about asp.net web api, i was very excited about it but in between i had that mmmmm moment. i was like, this is great but what about WCF? I am not going to create any WCF services anymore?  &lt;p&gt;so I had think again about it but could not find any concrete answer as these two are overlapping in many areas. so I had to do a bit more R&amp;amp;D about the differences and I came across &lt;a href="http://mattmilner.com/Milner/Blog/post/2012/02/28/WebAPI-or-WCF.aspx" target="_blank"&gt;this blog post from Matt Milner&lt;/a&gt;. &lt;p&gt;the post has got very fair point on when to use WCF services and when to use ASP.net web api. but in nutshell I think for most of our feature service development for web –over http-, we are going to use ASP.net web api and it kind of make sense as it’s much easier to setup and use. &lt;p&gt;here is blog post address: &lt;p&gt;&lt;a href="http://mattmilner.com/Milner/Blog/post/2012/02/28/WebAPI-or-WCF.aspx"&gt;http://mattmilner.com/Milner/Blog/post/2012/02/28/WebAPI-or-WCF.aspx&lt;/a&gt;&lt;/p&gt;</description><pubDate>Sun, 11 Mar 2012 12:00:42 GMT</pubDate><guid isPermaLink="true">http://old.taslimi.me:80/asp.net-web-api-vs-wcf-service</guid></item></channel></rss>