CODEWITHSUNDEEP
c#wcfasp.net-2.0
C_Rance
C_Rance

Reputation: 661

.Net 2.0 consuming WCF

I am working on both the project using .Net 2.0 Web Application and also WCF. If I use the WCF by its default configuration, when the .Net 2.0 project call its method, it throws an exception for unsupported SOAP message.

Goggled and found that people mentioned that WCF need to change the binding to BasicHttpBinding ->http://msdn.microsoft.com/en-us/library/ms731134.aspx

Tried that and since I am hosting in IIS I did not do the BasicHttpBinding instantiation like the example shown below.

// Create a BasicHttpBinding instance
BasicHttpBinding binding = new BasicHttpBinding();

However this time round, I can't even run the WCF service. When I run using right click, view in browser, I get a page with

"Service name" has zero application (non-infrastructure) endpoints

My web config for WCF is exactly same as the link I have given, only that I have changed the contract to suit my file.

Anyone with experience that care to help? Thanks

The web.config

<system.serviceModel>
    <services>
      <service name="MyService" behaviorConfiguration="HttpGetMetadata">
        <endpoint address="" contract="MyContractName" binding="basicHttpBinding" />
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="HttpGetMetadata">
          <serviceMetadata httpGetEnabled="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>

Upvotes: 0

Views: 1799

Answers (1)

Aliostad
Aliostad

Reputation: 81700

Yes, I just did that today.

  • Define the WCF service with BasicHttpBinding
  • On your client, add web reference and it will create a SoapClient
  • If you need security you need to use WSE 2.0 SP3.

My case had a requirement for clear-text username/password with SSL and I happily got it working using this.

Upvotes: 1

Related Questions