Clever Geek Handbook

SVCUtil "link to update service" equivalent command parameters

I want to update service references in a Visual Studio 2010 solution using SVCUtil because this solution has multiple projects and it is not good to have the references update one by one.

I would like to know your point of view because I have to be sure that I am going to execute the same command as Visual Studio 2010, or even if Visual Studio 2010 does not use SVCUtil, the equivalent command for IDE behavior.

Many thanks.

+2


source to share


2 answers


Some googling here and here shows in VS 2008, although this will depend, of course, on your options in the additional options in the add service links wizard.

Edit: Agree. Never be afraid to ditch and recreate service links from scratch. When working with version control like TFS, it is often a mess to "update" service links as it shows you which files are wsdl, xsd and disco, etc. Have been changed, added or removed, etc. (And get filenames like SomeXSD92.xsd). It is generally faster to just discard and recreate them.



Johan's post makes a good point (and can be used as part of a standard design pattern called Service Agent that handles the client proxy implementation). I'm not really sure what you mean when you say that two levels should refer to the same assembly? If you share the types of the objects called in the service, you still need to reference the entity assembly in most levels. For your service agent build project (which has all the service references), you can republish the same Service Contract that is used by the WCF server, or migrate it to a new interface.

+1


source


The easiest way to update a lot of service references is to put everyone in a dedicated project. Link to this project from all projects that should use them. If the service link needs to be updated, you will only do it in one place.



+2


source






More articles:


All Articles