title: Creating WCF services in mono 2.8.2
body: <p>I had mono-2.6.7 installed and and a WCF service:</p>
  
  <pre><code>&lt;system.serviceModel&gt;
      &lt;behaviors&gt;
          &lt;endpointBehaviors&gt;
               &lt;behavior name="RestB"&gt;&lt;webHttp/&gt;&lt;/behavior&gt;
          &lt;/endpointBehaviors&gt;
      &lt;/behaviors&gt;
      &lt;serviceHostingEnvironment aspNetCompatibilityEnabled="true" /&gt;
      &lt;services&gt;
        &lt;service name="Rest"&gt;
          &lt;endpoint address="" behaviorConfiguration="RestB" binding="webHttpBinding" contract="Rest" /&gt;
        &lt;/service&gt;
      &lt;/services&gt;
  &lt;/system.serviceModel&gt;
  </code></pre>
  
  <p>It worked. </p>
  
  <p>I wanted to use multiple endpoints and I kept getting errors as soon as I specified the address, so I decided to try mono 2.8.2. After installing 2.8.2 (after adding serviceBehavior which mono complained about) I started getting:</p>
  
  <pre><code>
  "HttpListenerContext does not match any of the registered channels"
  System.InvalidOperationException: HttpListenerContext does not match any of the registered channels
    at System.ServiceModel.Channels.Http.HttpListenerManager.ProcessNewContext (System.ServiceModel.Channels.Http.HttpContextInfo ctxi) [0x00000] in :0 
    at System.ServiceModel.Channels.SvcHttpHandler.ProcessRequest (System.Web.HttpContext context) [0x00000] in :0 
    at System.Web.HttpApplication+c__Iterator2.MoveNext () [0x00000] in :0 
    at System.Web.HttpApplication.Tick () [0x00000] in :0 
  </code></pre>
  
  <p>when trying to access urls which worked in mono-2.6.7.</p>
  
  <p>I tried with both mod-mono-server2 and mod-mono-server4. </p>
  
  <p>I tried to look up this problem but I couldn't find anything. </p>
  
  <p>Could someone show me a working example of a WCF service in mono-2.8.2 or mono-2.6.7 configuration with multiple endpoints?</p>
  
  <p>UPDATE: After reverting to mono-2.6.7 the my service 'Rest' shown above works again. </p>
  
  <p>Thanks in advance gurus</p>
  
  <p>Thanks
  Tymek</p>