nservicebus

问题 In NSB 5, how do I correctly configure NSB with autofac container with one IDocumentStore for NSB data and a separate IDocumentStore for application data? I've pasted the relevant part of EndpointConfig below: // Raven DataStore for Freight system var appDataStore = new DocumentStore { ConnectionStringName = "RavenDB", DefaultDatabase = "ApplicationData" }; appDataStore .Initialize(); // Raven DataStore for NServiceBus var nsbDataStore = new DocumentStore { ConnectionStringName = "NServiceBus

问题 In NSB 5, how do I correctly configure NSB with autofac container with one IDocumentStore for NSB data and a separate IDocumentStore for application data? I've pasted the relevant part of EndpointConfig below: // Raven DataStore for Freight system var appDataStore = new DocumentStore { ConnectionStringName = "RavenDB", DefaultDatabase = "ApplicationData" }; appDataStore .Initialize(); // Raven DataStore for NServiceBus var nsbDataStore = new DocumentStore { ConnectionStringName = "NServiceBus

问题 On a recent project, I used NServiceBus to update multiple (typically two) MongoDB read models as a result of commands initiated by users. After reading more about MediatR it seems like, as the read models are part of this application (i.e. no other services are consuming the ISomethingHappened events), NServiceBus was probably overkill here. That said, the guaranteed delivery and retries that NServiceBus provides aren't necessary with MediatR, however for most applications, I can't afford to

问题 We are trying to get many applications to communicate together and drive actions in each other via NSB. I would like to put each app into its own queue for two reasons: make it easier for support to troubleshoot problems and (possibly) have another place where I could scale the app. The bus will be hosted inside a windows service, possible just single instance that all apps will share. Each app can publish a message that will be picked up by windows service and processed using assemblies from

问题 I am trying to get to grips with NSerivceBus and although it's mostly going smoothly I am struggling to understand how to configure the EndPointName. So for example, after following a few examples I have managed to come up with the following but any attempt I make to change the EndPoint Name fails. So the myServer queue is currently what it is named, taken, I think from the namespace here: namespace MyServer { class EndPointConfig : IConfigureThisEndpoint, AsA_Server { } } But when i Put

问题 I am using the FileShareDataBus in NServiceBus 3. Is there any support for cleaning up databus files? If not, what would be the best practice to achieve this (like how do you ensure that the file is not part of a message that is in the error queue)? 回答1: Given that it's impossible to know how long a message stay in the error queue I usually purge after a resonably long time (Max(SLA) + x days) 来源： https://stackoverflow.com/questions/12642468/cleanup-files-when-using-nservicebus

问题 I am attempting to inject an object into my saga. Using the following endpoint, when the message arrives at the handle method of the saga the property is null. The endpoint: public class EndpointConfig : IConfigureThisEndpoint, AsA_Server, IWantToRunAtStartup { public void Run() { IOrderRepository orderRepository = new OrderRepository(); Configure.Instance.Configurer.ConfigureProperty<CreateOrderSaga>(x => x.OrderRepository, orderRepository); } // stop method removed } The app.config <?xml

问题 I have a Console app within which you can specify parameters, based on the parameters specified various handlers will be loaded. For instance: prgm.exe nyse prgm.exe nasdaq The goal is that within my code I have INyseHandlers and INasdaqHandlers and in the first case only any handlers extending the former are loaded, similarly for the case of the latter. The goal is to have one program which can listen to various or all sources depending on how it is run. To achieve this, I have set up my

问题 I have a following situation: So, receiver subscribes to two kind of events: eventA and eventB. NServiceBus creates queue for receiver (Receiver) and places messages of type eventA and eventB to to same queue. Question is, if I can configure NServiceBus to use separate queues (ReceiverEventA and ReceiverEventB) for each type of event for receiver? Or can I have two receivers in single process (and each receiver separate queue). Thing is, that EventA takes much longer to process than EventB,

问题 I have a following situation: So, receiver subscribes to two kind of events: eventA and eventB. NServiceBus creates queue for receiver (Receiver) and places messages of type eventA and eventB to to same queue. Question is, if I can configure NServiceBus to use separate queues (ReceiverEventA and ReceiverEventB) for each type of event for receiver? Or can I have two receivers in single process (and each receiver separate queue). Thing is, that EventA takes much longer to process than EventB,