Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, thanks for buying the book! Yes, you can absolutely subscribe to events from the same AppDomain. Here are some thoughts as to what might be happening.</p> <ul> <li>Do you see log entries that indicate they are subscribing to the event? If not then they are not subscribing.</li> <li>You didn't post code for your command and event, so I'm not sure if you're using Unobtrusive Mode or directly implementing <code>IEvent</code>. NServiceBus 4 will not automatically subscribe to anything not recognized as an event.</li> <li>I see <code>InMemorySubscriptionStorage</code> in your code. This makes it a little difficult to actually look at that storage. You could try injecting an <code>ISubscriptionStorage</code> somewhere so that you can look at what's in there in the debugger. Or just switch to the default Raven subscription storage for awhile so that you can navigate to the RavenDB Studio at <code>http://localhost:8080</code> and look at the subscription documents.</li> <li>I'm not sure why you sealed your handler class. I can't think of a specific problem that might cause but it might be a good idea to take it out to eliminate it as a possible problem.</li> <li>Try separating your handlers into separate classes. There's no reason for one class to implement both anyway - the container will spin up new instances for each message so you can't share state, so it's probably best to not give another developer the impression that they could.</li> <li>Also <a href="http://groups.yahoo.com/neo/groups/nservicebus/conversations/topics/20570" rel="nofollow">this issue</a> could have something to do with it?</li> </ul> <p>And of course I get to be a broken record sometimes with this but I would <a href="http://www.make-awesome.com/2010/10/why-not-publish-nservicebus-messages-from-a-web-application/" rel="nofollow">caution you not to publish events from a web application in the first place</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload