Click here to Skip to main content
13,094,732 members (88,091 online)
Click here to Skip to main content
Add your own
alternative version

Tagged as


33 bookmarked
Posted 7 Mar 2013

Difference between Proxy and Channel Factory in WCF

, 7 Mar 2013
Rate this:
Please Sign up or sign in to vote.
In this article I will show you the differences between WCF channel factory and proxy and when to use them.


In this article I will show you the difference betweens a WCF Channel factory and Proxy and when to use a Proxy and when to use a Channel Factory.


There are three ways to create a WCF client:

  • Proxy
  • WCF Channel Factory
  • REST services, using HttpClient or WebClient

Using the code

Before going into the differences, I will explain what a WCF channel factory is and what a proxy is in WCF and when to use a Proxy and when to use a channel factory.

What is Proxy

Proxy is a CLR class that exposes a single CLR interface representing the service contract.

A proxy is the same as a service contract, but also has additional methods for managing the proxy life cycle and the connection to the service. The proxy gives the following details: its location, its implementation technology, and run time platform and communication transport.

A proxy can be generated in two ways:

  1. By using Visual Studio: by right clicking References and clicking on Add Service Reference. Then open the Add Service Reference dialog box where you have to specify the base address of the service and the namespace that contains the proxy.
  2. This auto generates proxy code that connects to the service by reading the WSDL (Web Service Descriptive language). If the service address changes for any reason you have to regenerate it. The big advantage of this is that it is easy to set up - Visual Studio has a wizard and it's all automatic. The disadvantage is that you're relying on Visual Studio to do all the hard work for you, and so you lose control.

  3. Using the SvcUtil.exe command-line utility. We have to provide SvcUtil with the HTTP-GET address or the metadata exchange endpoint address and, optionally, using svcutil.exe, it creates a proxy that derives from System.ServiceModel.ClientBase<TChannel>.

2. What is Channel Factory

Use the ChannelFactory class with a known interface. This depends on you having local interfaces that describe the service contract. The big advantage is that you can change more easily. But you still have to recompile and fix changes, but now you're not regenerating code, you're only referencing the new interfaces. Channel factory is commonly used when you have control of both the server and the client.

In ChannelFactory<T> you must share contract assemblies between the service and the client. That's why ChannelFactory<T> can save you time.

When your project shares a common service contract DLL between the client and the server, you have to use the ChannelFactory class.

For using channel factory, the following steps are necessary:

  1. Create a binding in WCF
  2. Create a ChannelFactory class
  3. Create a Channel
  4. Send-Receive messages over that channel


In the below example, we use the ChannelFactory class and we send messages back and forth to the service.

using System;
using System.ServiceModel;
using ClientConsole.ServiceReference;

namespace ClientConsole
    internal class Program
        private static void Main()
            var channelFactory =
                new ChannelFactory<IEchoService>(
                    "WSHttpBinding_IService" // endpoint name

            IService channel = channelFactory.CreateChannel();
            Message result = channel.Echo(
                new Message
                        Text = "Hey "  

            Console.WriteLine("Service given respond at {0}: {1}",


Difference between proxy and channel factory

Proxy Channel Factory
1 Only requires a URL where the service resides You must have direct access to the assembly that contains the service contract
2 Very simple Not easier
3 Easy to understand Channels are complex, network-related
4 Visual Studio gives you the Add the Reference option When you share a common service contract DLL between the client and the server, you'll be using the ChannelFactory class
5 Proxies have several restrictions like:
  1. Properties need to have gets and sets
  2. Constructors can't be exposed
  3. Methods other than the service contract cannot be exposed
If you know that your entities will not change much and the client code is less, then a DLL would work better than a proxy
6 By using SVCutil.exe, you can create a proxy When you are using a DLL that refers to the service contract interface then use the channel factory class

Good luck and please let me know your feedback! In this way you can learn the difference between a proxy and a channel factory.

If you have any queries, mail me at


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Sujit Bhujbal
Technical Lead
India India
Sujit Bhujbal is Senior Software Engineer having over 6 + years of Experience in 3.5,WPF,WCF and has worked on various platforms. He worked during various phases of SDLC such as Requirements and Analysis, Design and Construction, development, maintenance, Testing, UAT.

He is Microsoft Certified Technology Specialist (MCTS) in /WCF Applications. He worked at various levels and currently working as a Senior Software Engineer.

His core areas of skill are Web application development using WPF,WCF , C#.Net, ASP.Net 3.5, WCF, SQL Server 2008, CSS, Java script Web design using HTML, AJAX and Crystal Reports

He is proficient in developing applications using SilverLight irrespective of the language, with sound knowledge of Microsoft Expression Blend and exposure to other Microsoft Expression studio tools.

Microsoft Certified Technology Specialist (MCTS): Web Applications Development with Microsoft .NET Framework 4
Microsoft Certified Technology Specialist (MCTS): Accessing Data with Microsoft .NET Framework 4
Microsoft Certified Technology Specialist (MCTS): Windows Communication Foundation Development with Microsoft .NET Framework 4

Blog: Visit Sujit Bhujbal

Personal Website :-Visit sujit Bhujbal Personal Site

Facebook :- Sujit Bhujbal Facebook

CodeProject:- Sujit Bhujbal codeproject

DotNetHeaven:- DotNetHeaven


Linkedin :-Linkedin

Stack-Exchange: <a href="

You may also be interested in...


Comments and Discussions

GeneralMy vote of 5 Pin
Terespl7-Aug-13 1:55
memberTerespl7-Aug-13 1:55 
GeneralRe: My vote of 5 Pin
Sujit Bhujbal7-Aug-13 20:36
memberSujit Bhujbal7-Aug-13 20:36 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.170813.1 | Last Updated 7 Mar 2013
Article Copyright 2013 by Sujit Bhujbal
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid