In a lot of software systems, you'll either see a litany of different settings in a configuration file, or a single configuration value and a huge wall of settings in a switch statement in code. Not so with NServiceBus. NServiceBus uses a concept called profile to activate different options within an endpoint based on environment or capability.
Tip
Many of the dependency injection containers support a similar profile feature. Be sure to check the documentation for your favorite one!
A profile can be activated on an endpoint by including its full class name as a command line parameter, or by including it with the install options when installing an endpoint as a service. For instance, to run an endpoint with the Lite profile, as we have done in some of the examples in this book, run the following code:
> NServiceBus.Host.exe NServiceBus.Lite
All of the built-in NServiceBus profiles are located directly in the NServiceBus namespace. These profiles fall into two categories; environmental...