TopShelf VS Topper

Ultimately still might be worth looking into creating our own templates for common console app style applications. For example, with TopShelf I don't bother creating Windows Service template applications any longer. I just create a console app, include TopShelf, Unity, NLog... and instant no-fuss-no-muss self-installing, dependency injected, easily logged Windows Service.

I like using NuGet: TopShelf to control the service because it's a little more friendly than Visual Studio's default service manager, but even the default one works fine.

We've always used Topshelf: http://topshelf-project.com/

As you know, we're using Topper so that we can easily run our Rebus back end in the Azure App Service as continuous Web Job. This means we need to have the App Service configured as always on. We need to create a database for Rebus to use, but we're Rebus will create the tables if they don't already exist. The same is true for the queues in our Azure Service Bus. We need to change our configuration spells a little so that we can use these Azure resources.