JobHostConfiguration gone?

I have been using WebJobs in a dotnet core project, so I have code like this:

class Program
{
static void Main(string[] args)
{
var loggerFactory = new LoggerFactory();
using (loggerFactory)
{
IServiceCollection serviceCollection = new ServiceCollection();

            var cfg = ConfigureServices(serviceCollection, loggerFactory);

            var config = new JobHostConfiguration();
            if (config.IsDevelopment)
            {
                config.UseDevelopmentSettings();
            }

            config.Queues.MaxPollingInterval = TimeSpan.FromSeconds(10);
            config.Queues.BatchSize = 1;
            config.JobActivator = new ServiceJobActivator(serviceCollection);
            config.UseTimers();
            config.LoggerFactory = loggerFactory;

            var host = new JobHost(config);

            host.CallAsync(typeof(WebJobsMethods).GetMethod("ProcessMethod"));

            host.RunAndBlock();
        }
    }

This is deployed along with a netcore webapi to an Azure App Service. This code doesn’t compile any more due to JobHostConfiguration being gone… but it probably goes way deeper than that!

Maybe the approach is completely different now? Where do I find the new pattern? Including configuring DI? My webjobs has a continuous job, some timer triggers, and a queuetrigger, configures DI, uses application insights, and logs.

[KalyanChanumolu-MSFT]

Microsoft.Azure.WebJobs 3.0.1 was released last night & I tried upgrading from 3.0.0-beta5. I see that JobHostConfiguration is missing RunAndBlock() is missing from JobHost QueueTrigger Attribute is missing.

What are the equivalents for these?

[mathewc]

The sample here shows the new host configuration process for a continuous WebJob. That sample doesn’t add/use all possible extensions, it’s meant as a starting point/sample. More notes to answer various questions added above:

• in general all the previous config.UseXXX extension methods migrated to IHostBuilder builder.AddXXX methods. As in the sample here
• In order for the builder.AddXXX methods to be present in your solution, you have to add the relevant nuget package for the extension you’re trying to use. E.g.:
  • to use any of the Azure Storage bindings (Queues/Blobs/Tables) you have to add the Microsoft.Azure.WebJobs.Extensions.Storage package and call builder.AddAzureStorage(). You’ll also generally want to call builder.AddAzureStorageCoreServices() to register the storage based implementations of various system services (singleton blob lease management, etc.). This was a big change from v2 - all the Azure Storage bindings used to be baked into the core WebJobs package. We’ve moved them out into their own extension package.
  • to use ServiceBus you have to add the Microsoft.Azure.WebJobs.Extensions.ServiceBus package and call builder.AddServiceBus(). Note that there was an package rename here to standardize our extension package naming. The package used to be called Microsoft.Azure.WebJobs.ServiceBus - don’t use that one in v3.
  • to use Timers you have to add the Microsoft.Azure.WebJobs.Extensions package and call builder.AddTimers(). To use timers, you also need to call builder.AddAzureStorageCoreServices() because timers rely on blob leases behind the scenes
  • and so on for the other extensions. Look for the relevant Microsoft.Azure.WebJobs.Extensions.XXX package, add it to your project and call the builder AddXXX method.
• to use Application Insights, call builder.AddApplicationInsights() as in the sample here.
• Yes host.RunAndBlock() is gone - the new pattern is shown in the sample I linked to above (here). I.e. call await host.RunAsync() from your async main method after building the host