Sorry for the rather large delay in this week’s NServiceBus Weekly. Things have been rather hectic lately (see here, here and here) but I’m trying to get back to the normal schedule in the next episode.
- Project Changes - Current revision: 1379. It seems that NServiceBus will get a new configuration model at some point, as pointed out by the revision 1370. Overall, we saw ten new revisions last week so the NServiceBus team isn’t sitting idle.
Tutorials and Articles
- Support for child containers in NServiceBus – Andreas Öhlund reports about a new feature present in the NServiceBus trunk: Support for child containers. Check out Andreas’ post for details and usage tips. Thanks goes to Jonathan Oliver for supplying the feature.
- Getting Started with NServiceBus Part 6: MVC Music Store Saga(Workflow) – Another great post by Adam Fyles, this time concentrating on the saga-support in NServiceBus.
- NServiceBus, WCF and WebService – Frank Mao sheds some light on how to expose NServiceBus as a WCF service.
- Are NServiceBus handler’s members safe for storing message related (and not related) data? – Interesting question asked by Rationalle. From David’s answer we learn that by default, every call on a message handler will happen against a new instance.
- Testing Bus.Send in an application using NServiceBus – Mgamer likes to know how to test methods which call Bus.Send. Check out the answers by arootbeer and Adam Fyles for answers.
- The CQRS Kitchen – Here’s an interesting open source project from Codeplex: The CQRS Kitchen. The project is an example application which demonstrates how one can implement CQRS. NServiceBus is one of the techniques used to implement the app.
- Configure.WithWeb and Spark view engine problems – Dkode8880 is reporting that the Spark view engine for ASP.NET applications doesn’t mix in well with the NServiceBus.
- How to handle errors and ensure delivery of messages – Read on to find out more information on how NServiceBus and MSMQ try to ensure the delivery of messages.
- Specify a handler to run last – Udi pops in to answer the question presented by jontycurtis. From this thread one can learn why there isn’t support for specifying the last message handler.
See you again in few days.