c# - WSDL-First approach, not same WSDL deployed -


here approach (don't hesitate tell me if doing wrong) :

-write xsd files defining objects

-use wscf.blue generate wsdl accordingly xsds

-use wscf.blue generate web service code

-implementing stub , exposing svc

so far, not facing problem. can access .svc through browser. thing deployed wsdl not same designed one.

when tried test service soap ui , designed wsdl source, failed because wsdl differents. when tried deployed one, works fine.

same result when tried generate client (console application) designed wsdl (with svcutil.exe) : fails same way (contractfilter mismatch @ endpointdispatcher exception). works add service reference.

i won't develop client people will work on wsdl had give them first. there way work designed wsdl or had give them deployed 1 ?

thanks in advance.

excuse me english, not native speaker.

yes can expose own wsdl (using example data wscf.blue walkthrough), externalmetadatalocation being important part:

  <system.servicemodel>     <behaviors>       <servicebehaviors>         <behavior name="mybehavior">           <servicemetadata httpgetenabled="true" externalmetadatalocation="../contractmetadata/restaurantservice.wsdl"/>         </behavior>       </servicebehaviors>     </behaviors>     ...     <services>       <service name="restaurantservice.restaurantservice" behaviorconfiguration="mybehavior">         ...       </service>     </services>   </system.servicemodel> 

but haven't had luck making work in conjunction "add service reference". vs keeps generating code isn't compatible webservice generated wscf.blue.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -