azure-webjobssdk

I've got a webhook-triggered Azure WebJob. For... reasons, I do not have control over the system that is sending the webhooks. One webhook per day is sent. It is the only WebJob hosted by the WebApp. During testing I wanted to disable this WebJob, so I stopped the WebApp. Much to my surprise, the WebJob ran even though the WebApp was disabled. So my question is two-fold: Is the ability to trigger a WebJob while a WebApp is disabled intentional, or did I encounter some sort of bug? If this is intentional, is there a way to disable this job being triggered via the Azure portal? If the only

I have implemented a long running process as a WebJob using the WebJobs SDK. The long running process is awaited because I want the result. public async Task ProcessMessage([ServiceBusTrigger("queuename")] MyMessage message) { await Run(message.SomeProperty); // takes several minutes // I want to do something with the result here later.. } What I can't figure out is why the message sometimes is abandoned which of course triggers the handler again. I've tried to debug (locally), setting breakpoints before ProcessMessage finishes and I can see that it appears to finish successfully. The Sevice

I created an on-demand webjob. In the management portal there is no option to upload a new zip, to update it. I can delete the existing webjob and create a new one, but I would like to keep my logs. Is there any way to re-deploy it, overriding the old version, maintaining the logs? lopezbertoni You can connect to the website where the webjob is at via FTP and update the necessary files without erasing your log files. You can get the credentials to connect via FTP from the Publish Profile. You can also use your website's debug console at: https://yoursitename.scm.azurewebsites.net/DebugConsole

I have the following scenario: I have an azure webjob (used to send mails) and I need to check the progress of the webjob in my web application. I am using SignalR to communicate with clients from my server. When I want to send an email, I push a message in the queue and the azure webjob does his job. The question is, how can I communicate the progress of the webjob to the client? Originally my idea was to push a message from the webjob, so the Hub could read it from the queue. Then, I would notify clients from the hub. However, I am not able to find a way to communicate the webjob and the hub

I just used the WebJob SDK to add a WebJob to my web app. Now, when publishing the web app, VS is stuck when publishing (does not hang, but does not progress either). I know it's caused by the WebJob because when I remove the webjobs-list.json , it publishes perfectly. Weird thing is, publishing the WebJob alone (using Publish as Azure WebJob ) does not present this problem. Using .NET Framework 4.5.1 if it matters. Update: 4.5 did not make a difference. Here's an image of the problem: Setting the "maximum number of parallel project builds" to 1 (default is 4) solved the problem for me. It is

I'm using a Webjob with the Windows Azure Storage SDK. When a new item shows up in a Queue, a method in my class is invoked. According to the SDK docs , if I take a TextWriter as a parameter to my method, the SDK will provide me with a TextWriter that I can write to which will show up in the Webjob's logging infrastructure. This makes it pretty easy to diagnose issues and troubleshoot things. public async static void ProcessQueueMessage([QueueTrigger("queueName")]MyModelType model, TextWriter logger) { await logger.WriteLineAsync(string.Format("Processing Item {0}", model.SasUrl)); // Some

I created a new Azure WebJob project in Visual Studio 2015 using .NET Framework 4.6. In the app.config, I set three connection strings: AzureWebJobsDashboard AzureWebJobsStorage MyDatabaseConnectionString The AzureWebJobsDashboard and AzureWebJobsStorage connection strings are identical and they're both pointing to my storage account. I'm including one of the connection strings -- since they're both identical, except the "name". <add name="AzureWebJobsDashboard" connectionString="DefaultEndpointsProtocol=https;AccountName=mystorageaccountname;AccountKey

I'm trying to do a bit of a balancing act here. Currently Azure WebJobs don't support .NET Core. With some help, I created a .NET Core Console App and made it work as a WebJob. On top of that I'm trying to implement Ninject for DI. Code compiles fine but when I run it, I'm getting the "No parameterless constructor is defined for this object." error -- see below. I may be in a bit of unchartered territory here with Azure WebJobs, .NET Core 2.0 and Ninject but any idea what may be causing this? BTW, I had the same exact code running as a WebJob targeting .NET Framework. I needed to migrate to