.net 1.1 client for WCF web service
-
Hi We are creating webservices on .net 3.0 using WCF, But since we have our old consumers still not migrated to 3.0/2.0, We need to created proxy for WCF service in .Net 1.1 I tried creating proxy from the with my wcf url http://localhost/myservice.svc?wsdl but it generated everything but not the proxy client inside in it. Any help is appreciated in this area. Thanks, SVM
-
Hi We are creating webservices on .net 3.0 using WCF, But since we have our old consumers still not migrated to 3.0/2.0, We need to created proxy for WCF service in .Net 1.1 I tried creating proxy from the with my wcf url http://localhost/myservice.svc?wsdl but it generated everything but not the proxy client inside in it. Any help is appreciated in this area. Thanks, SVM
Did you expose end points for an old style web service?
Cheers, Karl» CodeProject 2008 MVP My Blog | Mole's Home Page | How To Create Screen Capture Videos For Your ArticlesJust a grain of sand on the worlds beaches.
-
Did you expose end points for an old style web service?
Cheers, Karl» CodeProject 2008 MVP My Blog | Mole's Home Page | How To Create Screen Capture Videos For Your ArticlesJust a grain of sand on the worlds beaches.
<system.serviceModel> <services> <!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages --> <service name="FAService" behaviorConfiguration="FAServiceBehaviour"> <endpoint contract="IFAService" binding="wsHttpBinding" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="FAServiceBehaviour"> <serviceDebug includeExceptionDetailInFaults="true" /> <serviceMetadata httpGetEnabled="true" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> This is the End point for the new WCF Service, but do I need to set anything for consuming in the old style.
-
Did you expose end points for an old style web service?
Cheers, Karl» CodeProject 2008 MVP My Blog | Mole's Home Page | How To Create Screen Capture Videos For Your ArticlesJust a grain of sand on the worlds beaches.
<system.serviceModel> <services> <!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages --> <service name="FAService" behaviorConfiguration="FAServiceBehaviour"> <endpoint contract="IFAService" binding="wsHttpBinding" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="FAServiceBehaviour"> <serviceDebug includeExceptionDetailInFaults="true" /> <serviceMetadata httpGetEnabled="true" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> This is the End point for the new WCF Service, but do I need to set anything for consuming in the old style.
-
<system.serviceModel> <services> <!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages --> <service name="FAService" behaviorConfiguration="FAServiceBehaviour"> <endpoint contract="IFAService" binding="wsHttpBinding" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="FAServiceBehaviour"> <serviceDebug includeExceptionDetailInFaults="true" /> <serviceMetadata httpGetEnabled="true" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> This is the End point for the new WCF Service, but do I need to set anything for consuming in the old style.
endpoints usually have an address associated with them so that WCF knows where to listen.
Cheers, Karl» CodeProject 2008 MVP My Blog | Mole's Home Page | How To Create Screen Capture Videos For Your ArticlesJust a grain of sand on the worlds beaches.
-
<system.serviceModel> <services> <!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages --> <service name="FAService" behaviorConfiguration="FAServiceBehaviour"> <endpoint contract="IFAService" binding="wsHttpBinding" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="FAServiceBehaviour"> <serviceDebug includeExceptionDetailInFaults="true" /> <serviceMetadata httpGetEnabled="true" /> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> This is the End point for the new WCF Service, but do I need to set anything for consuming in the old style.
We encountered the same problem. The short answer is that you need to either switch to, or also expose, a basicHttpBinding. Clients in .NET 1.1 (ie. non-WCF) cannot communicate with a wsHttpBinding.
-
We encountered the same problem. The short answer is that you need to either switch to, or also expose, a basicHttpBinding. Clients in .NET 1.1 (ie. non-WCF) cannot communicate with a wsHttpBinding.
thanks it worked now, I also tried successfully doing the the multiple binding and endpoints.