Rhino Service Bus comes with a very simple to use service host. Use this when your application needs to run as a Windows Service. The host expects your class library to have at least one implementation of AbstractBootstrapper. By default this will register with the container all  IMessageConsumer implementations for the assembly being hosted.

Options for Rhino.ServiceBus.Host.exe

• /Name:<string> - [required] The service name that the host will use to create the windows service.
• /Assembly:<string> - [required] The full path to the assembly that will be hosted, must contain a class that implements AbstractBoostrapper.
• /ConfigFile:<string> - [optional] The full path to the applications configuration file.
• /Action:<string> - [required - Install, Debug, Server, Uninstall, Deploy] Install is used for the initial windows service installation. Debug is used when running from Visual Studio (sample below). Server is only used from the Windows Service and cannot be used directly. Uninstall removes the Windows Service. Deploy is used from the installer for the initial deployment.
• /BootStrapper:<string> - [optional] The type of BootStrapper to use. Only needed when assembly contains more than one BootStrapper.
• Account:<string> - [optional, MSMQ only] Used to setup the appropriate permissions when initially creating the queues.
• Host:<string,string> - [optional] First argument is the type that implements IApplicationHost. Second argument is the assembly path containing the implementation of IApplicationHost.

 

When running under Visual Studio

Use the settings below when you need to Debug both client / server from within the same solution.

 

Solution Property settings.

Last update: 6/13/2010 12:44:40 AM