title: The dreaded "No endpoint configuration found in scanned assemblies" NServiceBus error
body: <p>Background: </p>
  
  <ul>
  <li>I have two NServiceBus endpoint projects in my solution. </li>
  <li>Both are NServiceBus subscribers and contain a message handler to one message. </li>
  <li>Each subscriber project handles a message from one of two different publishers. As such, one project references a messages DLL from one publisher, and the other references a messages DLL from the other publisher. </li>
  <li>Both publishers are external to my solution. </li>
  <li>Apart from the messages DLLs, both subscriber projects reference the same binaries for NServiceBus, and additionally have the exact same setup (UnicastBusConfig, EndpointConfig, appSettings, etc) </li>
  </ul>
  
  <p>One subscriber project runs fine, but the other one fails with this error:</p>
  
  <p>Unhandled Exception: System.InvalidOperationException: No endpoint configuration found in scanned assemblies. This usually happens when NServiceBus fails to load your assembly contaning IConfigureThisEndpoint. Try specifying the type explicitly in the NServiceBus.Host.exe.config using the appsetting key: EndpointConfigurationTypeScanned path: <em>my path here</em>
     at NServiceBus.Host.Program.ValidateEndpoints(IEnumerable`1 endpointConfigurationTypes)
     at NServiceBus.Host.Program.GetEndpointConfigurationType()
     at NServiceBus.Host.Program.Main(String[] args)</p>
  
  <p>My suspicion is that the problem must lie with the NServiceBus publisher messages DLL of the subscriber which is failing to start up. Howerver, I am not sure how to work out what is wrong with this. I have looked at:</p>
  
  <ul>
  <li>both the NServiceBus publishers messages DLL's manifests using ildasm and they are identical (with regards to processor flags and NServiceBus DLL versions referenced). </li>
  <li>the NSB messages projects, which were both built with .Net 3.5 Framework.</li>
  </ul>
  
  <p>I am going insane here and have burned almost a day trying to get this working. Any help would be massively appreciated.</p>