Publish / Subscribe with nServiceBus tutorial

You may also like...

5 Responses

  1. Dries Marckmann says:

    I followed your tutorial, using the nservicebus NuGet package (NuGet FTW!!!) in a WCF project hosted in IIS7 but experienced a strange issue. I got the error:

    :Could not load file or assembly ‘System.Data.SQLite’ or one of its dependencies. An attempt was made to load a program with an incorrect format.”

    To solve this I had to set the “Enable 32-bit applications” in the advanced settings of the Application pool to True.

    After that it worked like a charm! Thanks!

  2. Tal McMahon says:

    For others stuck like I was, This post states
    “If the publisher is on ServerA, we should set UnicastBusConfig’s Endpoint to [email protected]

    That is in fact backwards.
    You should set the Endpoint to [email protected]

    hope that helps


  3. Dennis van der Stelt says:

    Thanks Tal, I changed the post to match your comment. Sorry for confusion! 🙂

  4. kris says:

    I don’t like this behavior: “nServiceBus will iterate over all assemblies and classes to find out which ones implement the IHandleMessages interface”. As I understand this mean nServiceBus will load all assemblies into memory to scan. It’s not good for large solutions. Is it possible to avoid this behavior and say to nServiceBus to scan only selected assemblies?

  5. Dennis van der Stelt says:

    Yes it is, but I don’t get why it’s a problem.

    First of all, it doesn’t load them all in memory so that it would become a memory problem. Second, if you have so many assemblies that you think it might become a memory problem you either have only 1MB of memory in your system or you have way, waaaay too many assemblies. Make smaller applications?! 🙂

Click on a tab to select how you'd like to leave your comment

Leave a Reply

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