The rationale for this statement from the author is as follows:
To get started, let me start by reminding everyone that you should never use the “Add Service Link” in Visual Studio to create a magic service. The code is incredibly detailed, difficult to manage, changes are rewritable and almost always used as an excuse not to learn WCF. There are a few things that are worse than dealing with people who know the product, simply because they know how to use the mouse.
As someone who relied on “Add Service Link” in Silverlight, I find this to be a little higher. I agree that the automatically generated code is verbose and cannot be edited because it will be overwritten. However, as far as manageability goes, it does not become simpler, in response to a change in my service, it takes one click to return the link to the service back.
Despite this, I think the article is very good, and I can guarantee that the ease of adding links to services prevents me from delving deeply into WCF. This is not necessarily bad, because at the end of the day, WCF works in plumbing, and I'm interested in writing an application that does not become a WCF expert. Be that as it may, I have reached a point where I encounter some serialization issues between Silverlight and my service, which I suspect are browser related. I need to dig deeper into WCF to figure it out, and this article looks like an ideal starting point.
The “Add Service Link” has been wonderful for me for 1.5 years, and although there are benefits to learning about the internal components of WCF, of course, there’s definitely nothing wrong with quickly and simply selecting a point and clicking to start with in visual studio.