C# – Calling a WCF service endpoint

cwcfweb services

I have created a WCF service with an endpoint, hosted in IIS, with a .svc file. When I hit the endpoint I get:

enter image description here

So it look like the end point is up.

I have created a Service Contract

[ServiceContract]
public interface ImyService
{
   [OperationContract]
   String GetSearchResults();
}

And created a class

[AspNetCompatibilityRequirements(RequirementsMode=AspNetCompatibilityRequirementsMode.Allowed)]
public class myService : ImyService
{
    public String GetSearchResults()
    {
        return "Hello World";
    }
}

How do I call the GetSearchResults method in the browser?

Edit

The binding is:

<bindings>
  <basicHttpBinding>
    <binding name="customBasicHttpBinding">
      <security mode="TransportCredentialOnly">
        <transport clientCredentialType="Ntlm"/>
      </security>
    </binding>
  </basicHttpBinding>
</bindings>

Best Answer

You cannot test the result of the WCF service in browser. You can test it using the WCF Test client. In your IDE just open your .svc or .svc.cs file and then click F5 which should launch the WCF Test client.

NOTE: Your project type is WCF Service Application Project

Also set the below in your web.config to enable metadata exchange.

<serviceBehaviors>
    <behavior>
    <serviceMetadata httpGetEnabled="true"/>
    <serviceDebug includeExceptionDetailInFaults="false"/>
    </behavior>
</serviceBehaviors>

Related Solutions

C# – Calling the base constructor in C#

Modify your constructor to the following so that it calls the base class constructor properly:

public class MyExceptionClass : Exception
{
    public MyExceptionClass(string message, string extrainfo) : base(message)
    {
        //other stuff here
    }
}

Note that a constructor is not something that you can call anytime within a method. That's the reason you're getting errors in your call in the constructor body.

Wcf – ContractFilter mismatch at the EndpointDispatcher exception

A "ContractFilter mismatch at the EndpointDispatcher" means the receiver could not process the message because it did not match any of the contracts the receiver has configured for the endpoint which received the message.

This can be because:

You have different contracts between client and sender.
You're using a different binding between client and sender.
The message security settings are not consistent between client and sender.

Have at look at the EndpointDispatcher class for more information on the subject.

So:

Make certain that your client and server contracts match.

If you've generated your client from a WSDL, is the WSDL up-to-date?
If you've made a recent change to the contract, have you deployed the right version of both client and server?
If you've hand-crafted your client contract classes, make sure the namespaces, elements names and action names match the ones expected by the server.

Check the bindings are the same between client and server.

If you're using a .config file to manage your endpoints, make sure the binding elements match.

Check the security settings are the same between client and server.

If you're using a .config file to manage your endpoints, make sure the security elements match.

Best Answer

Related Solutions

C# – Calling the base constructor in C#

Wcf – ContractFilter mismatch at the EndpointDispatcher exception

Related Topic