Where did QueueTrigger attribute go?

[johnkwaters]

I tried upgrading from 3.0.0 beta5 to beta8, and [QueueTrigger] no longer resolves when compiling

[xt0rted]

These are part of a new Microsoft.Azure.WebJobs.Extensions.Storage package

[johnkwaters]

Thanks, just downloaded it and found it! But now I can't find where JobHostConfiguration went :-)

[johnkwaters]

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();
        }
    }`

Maybe the approach is completely different now? Where do I find the new pattern? This is deployed along with a netcore webapi to an Azure App Service

[xt0rted]

You're right, there's a whole new way to configure webjobs that's based on the generic host which is similar to the asp.net host. Here's an example of the new setup https://github.com/Azure/azure-webjobs-sdk/blob/00686a5ae3b31ca1c70b477c1ca828e4aa754340/sample/SampleHost/Program.cs

[bmeijwaard]

I am not going to switch to 3.0.0 from 3.0.0-beta5 because the whole thing needs to be reworked. Thanks a lot for breaking changes.

[sonicmouse]

There is zero documentation on this breaking change. Could someone please convert this to the new way? A code snippit tells me nothing. It explains zero things.

			var jobConfig = new JobHostConfiguration(cfg.DocumentDatabase.BlobStorageServer)
			{
				NameResolver = new Support.BlobNameResolver(_env)
			};
			jobConfig.Queues.MaxPollingInterval = TimeSpan.FromSeconds(_pollSeconds);

			_wjHost = new JobHost(jobConfig);

Really what i need to know if how to set up a NameResolver using the new methods

ETA:
Here is my hack-job to get this working as it was in the above code:
https://stackoverflow.com/a/53179508/1204153

[onionhammer]

This team is the worst with regard to breaking changes.

[Davy-F]

So how come when I create a new WebJob project in Visual Studio with the latest updates it uses the old, invalid configuration?

And using the new way I get an assortment of errors:

1. IWebJobsBuilder does not contain a definition for AddWebJobsLogging...
2. IConfigurationBuilder does not contain a definition for AddCommandLine
3. ILoggingBuilder does not contain a definition for AddConsole...

This is with the "latest stable" package versions. What package versions am I meant to be using?

[pkaminsky]

You're right, there's a whole new way to configure webjobs that's based on the generic host which is similar to the asp.net host. Here's an example of the new setup https://github.com/Azure/azure-webjobs-sdk/blob/00686a5ae3b31ca1c70b477c1ca828e4aa754340/sample/SampleHost/Program.cs

Of what benefit is it for them to try to share a common generic host builder, when there is nothing common or generic about the host? This is a thing that happens at the start of an application, where the abstractions haven't even started yet and you're declaring, in definite and specific terms, exactly what you want to happen. It's the rest of the code that needs to be agnostic to the type of app it's running in. Building the host is where you declare unambiguously what type of app is running.

Taking it a step farther than the rest who downgraded their SDK, I literally switched off Azure Webjobs entirely as a direct result of this change. Worst.

[ddelapasse2]

Wow, nothing more fun than expecting to spend a couple of hours doing something you've done successfully before to find that the process has completely changed and no longer works! Is it impossible to use WebJobs with .NET framework now? I can't tell if we're supposed to be able to include some Core libraries or if we have to completely switch to it to make this work? VS 2017 sample. Wow, this is really terrible!!! Two hours of googling and I'm no better off than when I started.

Can anyone point me to a simple example using a SCHEDULED webjob in C# .NET F/W - I don't need processing queues or anything fancy. Just some maintenance work that should be done every day to clean up expired assets.

[nicholastic]

I'm so confused, so if we create a WebJobs project and upgrade all the packages, it totally breaks.

Is this upgraded project still the old .NET Framework or has updating all these packages made it a .NET Core project? There is no information on this or how to get it compiling.