Last post Oct 13, 2013 09:26 PM by Rion Williams
Oct 13, 2013 05:03 PM|James Dean|LINK
what is this WCF ? i used web services little bit but don't know about theses WCF, read a lot on google but couldn't get its technical terms like http://www.codeproject.com/Articles/139787/What-s-the-Difference-between-WCF-and-Web-Services or
It says like communcation over HTTP and SOAP , serialization, soap etc but yet i'm not qualified to understand these. Help me, guide me and please in easy wordings.
+ how to use in ASP.net ?
Oct 13, 2013 05:49 PM|speshulk926|LINK
WCF is Web Service on Steroids. You can do everything that you can do with a Web Service plus a ton more. For instance, you can actually create a web service that runs as a windows service instead of just a web service. I think the link you posted gave
great resource and if you follow it, you should be able to build one as it shows a basic example and a download of it. It also shows how to implement it from the client.
Oct 13, 2013 08:27 PM|jats_ptl|LINK
Hi James Dean.
WCF - Windows Communication Framework - is Microsoft's framework to make inter-process communication easier. It let's you do this communication through various means, plain old asmx web
services, Remoting, MS Message Queuing, and a couple more.
It let's you talk with other .NET apps, or non-Microsoft technologies (like J2EE). It's extensible enough to allow for newer stuff, like REST too (I don't think REST is built-in).
It's Microsoft's attempt to sort out and simplify network programming. It's provide an easy to use level of abstraction over different communication protocols and transportation methods. It's allows you to concentrate more on what you
want to implement rather than thinking on how to implement.
How to use WCF with ASP.NET?
Hope this helps.
Oct 13, 2013 09:26 PM|Rion Williams|LINK
Windows Communication Foundation or WCF is a framework that was designed by Microsoft to construct and build Web Services that can be used to provide an API and other services to other web applications. Web Services are excellent if your application's architecture
calls for it and you have multiple applications that might need to work together and access some of the same data (such as passing data or other objects across).
I'll explain a few of the terms that you were referring to as being troublesome earlier as well :
If you need a bit more information on getting started using WCF within .NET, I would recommend the following resources :