<div>
<div class="content wysiwyg-content">
If I'm having problems binding to a WCF service but I can access it using a Web Reference, and I'm doing a read-only operation, is there any reason not to do that? <br />
Is there an advantage to persisting with the binding to get the WCF to work?
</div>
</div>


If I'm having problems binding to a WCF service but I can access it using a Web Reference, and I'm doing a read-only operation, is there any reason not to do that? 
Is there an advantage to persisting with the binding to get the WCF to work?

Using Web Service  instead of WCF

Windows Communication Foundation (WCF) is a tool used to implement and deploy a service-oriented architecture (SOA) to support distributed computing where services have remote consumers. It features a runtime and a set of APIs in the .NET Framework for building connected, service-oriented applications. Services typically have a WSDL interface (Web Services Description Language) that any WCF client can use to consume the service, regardless of which platform the service is hosted on. WCF implements many advanced Web services (WS) standards such as WS-Addressing, WS-ReliableMessaging, WS-Security, RSS Syndication Services, WS-Discovery, routing and better support for REST services.