How to consume WCF web service through URL at run time?

Question

I want to access all the methods exposed in the service through the URL. if suppose the URL will be :

http://localhost/MyService/MyService.svc

How can I access methods:

1. if suppose I have a ServiceReference
2. and what should I do if don't have the Service Reference.

Solution 1

In order to use a WCF service, you will need to create a WCF client proxy.

In Visual Studio, you would right-click on the project and pick the "Add Service Reference" from the context menu. Type in the URL you want to connect to, and if that service is running, you should get a client proxy file generated for you.

This file will typically contain a class called MyServiceClient - you can instantiate that class, and you should see all the available methods on that client class at your disposal.

If you don't want to add a service reference in Visual Studio, you can achieve the same result by executing the svcutil.exe command line tool - this will also generate all the necessary files for your client proxy class for you.

Marc

UPDATE:
if you want to initialize a client proxy at runtime, you can definitely do that - you'll need to decide which binding to use (transport protocol), and which address to connect to, and then you can do:

BasicHttpBinding binding = new BasicHttpBinding();
EndpointAddress address = new EndpointAddress("http://localhost:8888/MyService");

MyServiceClient serviceClient = new MyServiceClient(binding, address);

But even in this case, you need to have imported and created the proxy client first, by using the "Add Service Reference" or svcutil.exe tools.

Solution 2

To answer how to do it without having a service reference. Have a look here (option #a):

Writing your first WCF client

You still need some reference (namely a reference to an assembly containing the contract / interface) but you do not make a service reference.

EDIT: Though the above is possible I would not recommend it. Performance is not exactly great when you have to generate the proxies like this. I usually use svcutil.exe and create an assembly containing my clients and create a reference to that assembly. This way you have more options for controlling what the proxies look like.

Solution 3

You can also make use of the WebClient class to call the WCF service without needing a service proxy. Effectively you can send and receive Strings and Binary data and also simulate POSTs.

I use it extensively for reusable components where the developer may not ever create the required proxy methods. A good comparison of ways to do POST is available here.

Solution 4

You call it with a /functionname, eg:

http://localhost/MyService/MyService.svc/GetVersionNumber

Edit:

How do you configure your method in the WCF service so you can call it directly from the browser?

I have an Interface:

[ServiceContract]
public interface IWebServiceImpl
{
    [OperationContract]
    [WebInvoke(Method = "GET",
        ResponseFormat = WebMessageFormat.Json,
        BodyStyle = WebMessageBodyStyle.Bare,
        UriTemplate = "GetVersionNumber")]
    string GetVersionNumber();

And a class to implement the GetVersionNumber method in the Interface:

public class WebServiceImpl
{
    public string GetVersionNumber()
    {
            return "1.0.0.0"; //In real life this isn't hard-coded
    }
}

Finally here is the Web.config configuration:

<system.serviceModel>        
    <diagnostics>
      <messageLogging logEntireMessage="true" logMalformedMessages="false" logMessagesAtServiceLevel="true" logMessagesAtTransportLevel="false" maxMessagesToLog="3000" maxSizeOfMessageToLog="2000"/>
    </diagnostics>        
    <bindings>
      <webHttpBinding>
        <binding name="webBinding">
          <security mode="Transport"/>
        </binding>
      </webHttpBinding>
    </bindings>
    <services>
      <service behaviorConfiguration="ServiceBehaviour" name="YOURWebServiceNameSpace.WebServiceImpl">            
        <endpoint address="" behaviorConfiguration="web" binding="webHttpBinding" contract="YOURWebServiceNameSpace.IWebServiceImpl"/>
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="ServiceBehaviour">
          <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
          <serviceMetadata httpGetEnabled="true"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="false"/>
        </behavior>
      </serviceBehaviors>
      <endpointBehaviors>
        <behavior name="web">
          <webHttp/>
        </behavior>
      </endpointBehaviors>
    </behaviors>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true"/>
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>

View more solutions