I copied a previous post to this one and deleted the emails from the previous post at the request of one of the people in the email. Unfortunately this causes the post to be out of sequence.
I agree, I started with this Blog but be wary!
Now we may turn our attention to the client application. To begin, let me start off by reminding everyone that
you shouldn't ever use "Add Service Reference" in Visual Studio for magical service client creation. The code is incredibly verbose, hard to manageable, edits are prone to being overwritten, and it's almost always used as an
excuse to not actually learn WCF. There are few things worse than having to deal with people who thing they know a product simply because they know how to use a mouse. There are reasons why
Juval Lowy, in all his books and talks, repeatedly tells people to avoid using this flawed feature. Fortunately, as professionals, we have the ability to
understand how to do things without magic.
The above excerpt from the mentioned link sent me on a long hard wild goose chase (considering the title of the blog). To make a very long story short I'll share correspondance that I had with a Silverlight Web Services Team member.
From: Yavor Georgiev
Sent: Monday, January 12, 2009 12:05 PM
To: Bill Kratochvil
Cc: CDF Silverlight Customer Issues
Subject: RE: (Silverlight Web Services Team) : SLSvcUtil - what is recommended P&P?
Thanks for your note.
I understand the scenario you are encountering in your enterprise app around managing config files. This is a common customer request and a command-line tool like svcutil is being considered in the next version of Silverilght.
Unfortunately we don't have any additional tips we can provide at this point. Please continue to follow our blog for SL3-related updates.
From: bill Kratochvil
Sent: Wednesday, January 07, 2009 7:21 PM
To: Yavor Georgiev
Subject: (Silverlight Web Services Team) : SLSvcUtil - what is recommended P&P?
Can the team provide guidance for consuming WCF service for enterprise level applications? My initial efforts were somewhat frustrating as the Silverlight forums have you going in circles looking for a SLSvcUtil that doesn't exist, or SVCUtil
flags that supposedly support Silverlight (that no one can reference).
The following blog highlights an issue with using Prism/CompositeWPF and Silverlight - the main assembly has to have a copy of the ServiceReferences.ClientConfig referenced in a module (separate assembly):
The above provides a simple solution for a single module that consumes a single WCF service. When we have 20+ modules, configuration promises to be quite the nightmare complicated by a cyle that has the solution moving through development, staging
and production environments.
"Add Web Service" doesn't seem to be a viable solution.
Your guidance and assistance will be appreciated as we have numerous sprints planned throughout the year that will be based on the infrastructure I provide; as an Independent Contractor I have a large responsibility to get this done right .
Global Webnet, LLC
This message was generated from a contact form at:
It was submitted by BillKrat
Your contact information was not shared with the user.