azure-webjobs

I attached a Web Job to my Azure website. The webjob prepares a file and I want to save it on a proper folder in the website. Environment.CurrentDirectory run on the script returns a path under a Temp directory: Temp\jobs\triggered\WEBJOBNAME\q0uwrohv.x5e I tried to go down on the directory tree: string path = Path.Combine(Environment.CurrentDirectory, @"..\..\..\..\..\Data") But it doesn't work: C:\DWASFiles\Sites\WEBSITENAME\Temp\jobs\triggered\WEBJOBNAME\q0uwrohv.x5e\..\..\..\..\..\Data How to make and save files from WebJob to a particular path? I don't want to use blob store. The path for

How do I create an Azure WebJob targeting .NET Core 1.1? In Visual Studio 2017, the only option I'm seeing for Azure WebJob targets .NET Framework -- see below. Under .NET Core, I don't see Azure WebJob listed. The VS 2017 tooling for .NET Core does not exist yet, although it is planned. It's still possible to write a Core based WebJob and deploy it manually to your Web App. But do note that the WebJob SDK (which is a whole other topic) does not yet support .NET Core (related issue here ). This is an extremely old question, but I just want to point out that WebJobs for .NET Core is now

I have an Azure webjob that I want to invoke from an Azure website. I want to pass string parameters from the website to the webjob. I know I can invoke the webjob as a REST API ( https://github.com/projectkudu/kudu/wiki/Web-jobs ). So I can invoke the webjob without any parameters: POST jobs/triggered/myjobname/run But adding parameters at the end doesn't appear to be working, i.e. jobs/triggered/myjobname/run?myparam1=value1 The information I see on using attributes in Microsoft.WindowsAzure.Jobs for binding doesn't mention my case, just binding to Azure storage items ( http://blogs.msdn.com

How can I reuse the TraceWriter object available in an Azure Function to log information in an externally referenced library? I tried passing in the object using the constructor and referencing the TraceWriter class (web.http.tracing). I didn't have luck as the classes seem different. Short version Use the Microsoft.Azure.WebJobs.Host.TraceWriter available in this nuget package . Alternatively, build your functions as a Web Project and you can debug locally. You can find a sample here . Long Version Your problem here is that you are using the wrong TraceWriter. I used the Azure Function logger

I an trying to publish my website along with few WebJobs but after the website and the jobs are created on the Azure Website, I see an error on the VS.NET 2013 that says: Error 948 An error occurred while creating the WebJob schedule: No website could be found which matches the WebSiteName [mysitename] and WebSiteUrl [http://mysitename.azurewebsites.net] supplied my website has 2 WebJobs, 1 that runs continuously and it's created and running, but the one that needs to be triggered on a schedule is having this problem. Any ideas as to what may be wrong here? Edit 1 Just wanted to add that the

I thought this would be a pretty straightforward task and there is quite a bit of documentation out there but I've had zero luck with any of it and am assuming that it is pretty much all out of date. I have .NET Core MVC 6 Web App that I've been developing for a while and need to set up a WebJob for it on Azure. I want to deploy this alongside the app using the continuous deployment system Azure provides that the app is already using. According to Kudu docs it's possible: https://github.com/projectkudu/kudu/wiki/Web-Jobs#deploying-net-console-webjobs-alongside-an-aspnet-application Which

I am planning to deploy a website to Azure, that will utilize Web Jobs . If the site is scaled up to run on multiple instances, should I expect the job to be started on all the instances as well (running concurrently), or can I expect there to only be one instance of the job running at a time ? Can this be configured in Azure ? I assume you are using Continuous WebJobs and not Manual/Scheduled. In that case, it will run on all the instances at once. For this to happen correctly, you need to be running in Standard mode, and have the Always On setting enabled. If you don't want it to run on all