web services - WCF / WSDL file seems to be malformed -


ok. have functional wcf rest service. can use fiddler , send json , expected responses.

so far good.

but when try add service reference in .net project throw error when try create service (please refer adding wcf service not add meaningful configuration.svc.info - think i’ve found root cause it’s sufficiently different decided open question.)

note it’s not visual studio. can add references other services fine , multiple different installs of vs won’t work service.

i think root cause wsdl file incorrect. there sample microsoft provides here - https://msdn.microsoft.com/en-us/library/windows/desktop/dd323317(v=vs.85).aspx , live example here - http://www.webservicex.com/globalweather.asmx?wsdl

the upshot both examples have lot more have when calling wsdl https://marius.activistmanager.com/1_0_0.svc?wsdl

but when use single page wsdl kinds of information - https://marius.activistmanager.com/1_0_0.svc?singlewsdl

i think it’s problem in wcf service’s web.config file set end point.

does see problem code cause problem discussed in other question? delighted find i'm doing stupid.

<client>   <endpoint address="https://apitest.authorize.net/soap/v1/service.asmx" binding="basichttpbinding" bindingconfiguration="servicesoap" contract="authorizenetcimtest.servicesoap" name="servicesoap" /> </client> <services>   <service name="marius.marius_1_0_0" behaviorconfiguration="metadatasupport">     <endpoint address="" behaviorconfiguration="marius.mariusaspnetajaxbehavior" bindingconfiguration="transportsecurity" contract="marius.marius_1_0_0" binding="webhttpbinding" />     <endpoint address="mex" binding="mexhttpbinding" contract="imetadataexchange" />   </service> </services>   <!--this transport services use. specifies connections have use https. since there no bindings http connections 404--> <bindings>   <basichttpbinding>     <binding name="servicesoap">       <security mode="transport" />     </binding>     <binding name="servicesoap1" />   </basichttpbinding>   <webhttpbinding>     <binding name="transportsecurity">       <security mode="transport">         <transport clientcredentialtype="none" />       </security>     </binding>   </webhttpbinding> </bindings>  <behaviors>   <servicebehaviors>     <behavior name="metadatasupport">       <!-- enables imetadataexchange endpoint in services -->       <!-- use "metadatasupport" in behaviorconfiguration attribute. -->       <!-- in addition, httpgetenabled , httpgeturl attributes publish -->       <!-- service metadata retrieval http/get @ address -->       <!-- "http://localhost:8080/sampleservice?wsdl" -->       <servicemetadata httpsgetenabled="true" policyversion="policy15" httpsgeturl="" />     </behavior>   </servicebehaviors>   <endpointbehaviors>     <behavior name="marius.mariusaspnetajaxbehavior">       <webhttp defaultoutgoingresponseformat="json" />     </behavior>   </endpointbehaviors> </behaviors> <servicehostingenvironment aspnetcompatibilityenabled="true" multiplesitebindingsenabled="true" /> 

john correct - here's description of problem (http://blogs.msdn.com/b/carlosfigueira/archive/2012/03/26/mixing-add-service-reference-and-wcf-web-http-a-k-a-rest-endpoint-does-not-work.aspx). looks option write code using restsharp. ugh.


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -