I have been debugging the Remote persistence we use for ECO6 – this uses WCF. It was Jonas that started this work and he did a fine job – but we have a few gotchas that I want to get documented here.

If you build your own server (Remote persistence server for ECO), either as WindowsService or as a WinForm application (both available from the ECO VS Wizard) we use the WCF class ServiceHost.

In this ServiceHost we set some parameters – like what binding to use and so on. During the beta-phase of ECO6 it became apparent that we also needed to set a lot of other values like MaxReceivedMessageSize and MaxBufferPoolSize etc on the Binding object.

That code came to look like this:

BasicHttpBinding binding = new BasicHttpBinding();

binding.MaxReceivedMessageSize = maxReceivedMessageSize;

binding.ReaderQuotas = System.Xml.XmlDictionaryReaderQuotas.Max;

binding.MaxBufferSize = int.MaxValue;

binding.MaxBufferPoolSize = 0; 

Uri address = new Uri(uri);

ServiceHost svc = new ServiceHost(t, address);

svc.AddServiceEndpoint(typeof(IPersistenceMapperWCF), binding, address);

The gotcha with this is that if you host your Remote persistence server in IIS – we do NOT use the ServiceHost because then IIS IS provides the ServiceHost for us.

So in this case we need to tune up the MaxReceivedMessageSize and MaxBufferPoolSize etc some other way : web.config.

So in your IIS hosted Remote Persistent Server you need to add something like this to your web.config:



    <service name="Frako.Emvis.PServerWebService.EmvisPMPWCF" behaviorConfiguration="TheBehavior">


      <endpoint address=""



                contract="Eco.Wcf.Common.IPersistenceMapperWCF"  />  








      <binding name="TheBindingConfiguration"              


        <readerQuotas maxStringContentLength="104857600"/>





  <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />



              <behavior name="TheBehavior">


        <serviceDebug includeExceptionDetailInFaults="true" />

        <dataContractSerializer maxItemsInObjectGraph="2147483646" />







Here is the same thing as an image with some hints:

The green line is the name of your service – this is the name of your subclass of the PersistenceMapperProvider.

The blue lines shows where we adjust some values to allow for bigger messages

The red lines just explains how reference and definition is separated


Having your own (enum) types

Another thing that got us stumped for a good 30 seconds was the unexpected server shutdown when trying to transfer types used by modlr-attributes over WCF when these types were not known to the service.

This is common place when you do your own Enumerations for example or any other handy attribute-type you might want to use.

You need to tell the WCF service about these types before the service is started. And you need to tell the client AND the server.

In a IIS hosted server use the Global.asax:

protected void Application_Start(object sender, EventArgs e)





And on the Client add it to Main:

static void Main()





When things do not work – complete darkness

Debugging the WCF issues was initially really annoying and complex – “Unexpected server shutdown” and nothing else…

But luckily it easy to turn on explicit logging in WCF. Go like this in the server web.config:





    <source name="System.ServiceModel"

            switchValue="Information, ActivityTracing"



        <add name="traceListener"


            initializeData= "c:\temp\WCFTracelog.log" />







This will give you a file with a lot of information at c:\temp\WCFTracelog.log.

Like when I had removed one of the AdditionalTypes.Add statements from above the log look like this:


This entry was posted in WCF. Bookmark the permalink.

2 Responses to WCF and ECO

  1. Pingback: WCF trouble-shoot | CapableObjects

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.