wsdl.exe

I have created two wsdl files with shared types imported from xsd schema file. After that I have created web services using interface generated by wsdl.exe tool with parameter /serverInterface. Frist web service, have web method “RegisterData” with put into queue some complex object to be processed, by system “A”. As result of this method is returned Boolean (with tell us that object was registered successful). Second web service, have web method “UpdateData” to update some data in system “B” based on this same object , with was changed in process on system “A”. So in system “A” I have to

Is it possible to get WSDL.exe to generate interfaces as well as, or instead of, concrete classes when it generates proxys to a web service? We're consuming a 3rd party webservice from an ASP.Net application, and have generated our proxy classes using WSDL.exe all well and good. I now want to write tests against my wrapper and business classes by faking out the web service. There is no interface or abstract base class to the proxy, and they are marked internal, meaning I can't inherit from them without putting my Fake/mock test code into my business project/assemblies. I could manually create

I have Visual Studio 2010 Ulitmate (with MSDN Premium), but I can't seem to find this file. I have tried installing the Visual Studio SDK but I can't seem to find the file. I have looked in: C:\Windows\Microsoft.NET\Framework\v3.5 C:\Windows\Microsoft.NET\Framework\v4.0.30319 C:\Program Files (x86)\Microsoft Visual Studio 10.0\SDK\v3.5 But I can't seem to find it. (In case you are wondering, I need it to perform these steps .) user213702 it should be under C:\Program Files (x86)\MicrosoftSdks\Windows\v7.0a\Bin . You should be able to use wsdl from visual studio command prompt and typing path

I am chipping away at building a client for a Java B2B web-service at the moment and I think I have identified the cause of a problem we have been having for quite some time. Unfortunately I'm unable to post the WSDL. Apparently my auto-generated proxy code (via wsdl.exe: have to use WSE 3.0 due to WCF not supporting password digest) is not able to handle the web-service's WSDL having multiple web-methods with the same complex return type. Take for example - a web-service that defines the following methods: Public ComplexTypeX Blah(); Public ComplexTypeX Blue(); Public ComplexTypeX Foo();