Heya 😃

So I’ve just started playing around / trying to use the TimerTrigger with a new webjob. I’m doing localhost development to make sure the code works, before I deploy it up to Azure.

To do this, I click F5 to Debug my webjob console app. Ok, great! works/etc… I then stop this (or the code throws an exception and crashes).

I then change one tiny thing and then hit F5 again … and then get this:

Sometimes, I wait 10 or even 20 seconds after the webjob stopped/stops and then hit F5 and still get that error.

Shouldn’t the host 100% tear down after it’s stopped? I should be able to hit F5, then close app, then hit F5 straight away, right?

Update / More info.

Here’s my program.cs as a reference:

    class Program
    {
        // Please set the following connection strings in app.config for this WebJob to run:
        // AzureWebJobsDashboard and AzureWebJobsStorage
        static void Main()
        {
            var config = new JobHostConfiguration();
            config.Tracing.ConsoleLevel = TraceLevel.Verbose;

            config.UseTimers();

            var host = new JobHost(config);
            host.RunAndBlock();

            //var host = new JobHost();
            //// The following code ensures that the WebJob will be running continuously
            //host.RunAndBlock();
        }
    }