svcutil.exe

I have .wsdl and .xsd files from WebService and need to generate proxy by them. Svcutil.exe and wsdl.exe generate very different output. What is the difference between these two tools for proxy generation and which way is more preferable? Svcutil and wsdl are two different technologies for generating a proxy for consuming your service. But wsdl.exe was made for old .NET 2.0 web services. It is like old version of svcutil. Svcutil allows you to generate proxies for both - web services and WCF services. For generating a proxy wsdl retieves the data by means of DISCO discovery protocol. Svcutil

I want to use svcutil to map multiple wsdl namespace to clr namespace when generating service proxies. I use strong versioning of namespaces and hence the generated clr namespaces are awkward and may mean many client side code changes if the wsdl/xsd namespace version changes. A code example would be better to show what I want. // Service code namespace TestService.StoreService { [DataContract(Namespace = "http://mydomain.com/xsd/Model/Store/2009/07/01")] public class Address { [DataMember(IsRequired = true, Order = 0)] public string street { get; set; } } [ServiceContract(Namespace = "http:/

After googling a bit there is no definite answer of whether Visual Studio 2008 uses svcutil.exe or not? Visual Studio 2005 did use it, but do the RTM versions of Visual Studio 2008 use svcutil? A few blogs say it doesn't (and make it seem surprising) SVCUtil & VS2008 Equivalent svcutil.exe command for VS2008 Add Service Reference SVCUtil Generating WCF client and the is field specified issue and other sites say it does. The reason I'm asking is we are flattening our WCF wsdl with a custom endpoint behavior extension (an implementation of IWsdlExportExtension/IEndpointBehavior) and using the

In our application we are forced to consume several WebServices. In the beginning we used just the "Add Service Reference" menu option, in order to create a WCF proxy. The wizard didn't generate a DataContract, but much rather an XML-Serializable class. So far, so bad, but this wasn't the killer. However, later we noticed, that we were losing data, because the generated proxy was adding the Order property when attributing and this was causing problems. Now we are trying to generate proxy classes from the WSDL using the SVCUTIL.EXE, but we are all the time getting the following error message: C

I'm having a WCF Service that uses wsHttpBinding. The server configuration is as follows : <bindings> <wsHttpBinding> <binding name="wsHttpBinding" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"> <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> <security mode="None"> <transport clientCredentialType="Windows" proxyCredentialType="None" realm="" /> <message clientCredentialType="Windows" negotiateServiceCredential="true" algorithmSuite="Default"

We have OSB services that are currently secured with a username and a password. I get a 401 unauthorized when attempting to generate a service proxy using svcutil. I know you need to set up a svcutil.exe.config file but I cannot find any examples except for one that passes a certificate. Dows anyone know how to send a username and password using svcutil? I don't think you can do that. What you can do in this case is either connect to that address in a browser and just download and save the WSDL file to your local disk and call svcutil.exe on that local copy - or ask the publisher of that

Is it possible to use svcutil to reuse/exclude referenced types, as with visual studio. I have multiple projects, my types/datamodels are stored in separate assemblies, so they can be used by other non wcf projects etc. When updating refrences in the visual studio gui, this all works out just fine. As long as a type is found on both sides of the border, it's excluded from beeing defined in the proxy. How can I achieve the same thing using svcutil? More clearly I want to generate the proxy from a dll, not a running service which contains the servicecontract. At the same time I want to feed the

I'm having a problem regarding namespaces used by my service references. I have a number of WCF services, say with the namespace MyCompany.Services.MyProduct ( the actual namespaces are longer ). As part of the product, I'm also providing a sample C# .NET website. This web application uses the namespace MyCompany.MyProduct . During initial development, the service was added as a project reference to the website and uses directly. I used a factory pattern that returns an object instance that implements MyCompany.Services.MyProduct.IMyService . So far, so good. Now I want to change this to use