WCF - Windows communication foundation - is the way we usually communicate between tiers with MDriven technology.

Turn on WCF-logging

WCF can be tricky since it is rather silent when it fails.

So if you have ruled out other issues and you still cannot get the communication to work turn on WCF-logging.

In most web.config we have left a commented block to turn on WCF-logging.

This is from the MDrivenServer:

You can find more info here:

https://www.capableobjects.com/2011/06/26/wcf-and-eco/

https://www.capableobjects.com/2012/01/06/wcf-trouble-shoot/

WCF and ECO

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:

<pre>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);</pre>