Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve found that I can import a SOAP/WSDL service that I plan on using into my solution either as a “Web Service Reference” (System.Web.Services) or as a “Service Reference” (System.ServiceModel / WCF).
I was wondering if what the differences were. I understand that ‘Add Service Reference’/WCF is newer, are there any disadvantages to using it over System.Web.Services or is it now the preferred way of consuming SOAP services in .Net?
The preferred and most useful way is indeed to use
Add Service Reference. This will add your service as WCF client side proxy.Add Web Referenceis the “old-style” ASMX/ASP.NET webservice way of doing things.WCF is the much better choice than ASMX, because:
Yes, WCF has a bad rap about being really hard to learn – I don’t really find that to be true. Check out those beginner’s resources – very useful indeed!