azure-webjobs

Deploy Azure WebJob using VSTS

南笙酒味 提交于 2019-11-28 09:21:36
I'm having some issues deploying an Azure WebJob using Visual Studio Team Services (VSTS). The WebJob seems to be deployed successfully but it breaks the Azure website that is hosted in the same App Service! I don't have this problem if I deploy using VS2013. This is my build task that generates the WebJob deployment package: And this is my deployment task: There are no errors when I deploy the Azure WebJob. If I go to the Azure Portal I see the WebJob is there, and it runs successfully. WebJob files are copied into the wwwroot\App_Data\jobs\triggered\RemoveExpiredDids folder as expected, but

Create a Scheduled Azure WebJob with PowerShell

人走茶凉 提交于 2019-11-28 08:33:53
I am trying to create an Azure WebJob to send a BrokeredMessage to an Azure ServiceBus Topic, the actual act of creating and sending the message is trivial however I have been unable to find a way to automate the creation of the Scheduled WebJob. The automated workflow should work as follows: Create a new Azure Website [Done] Create a new triggered Azure WebJob uploading a PS1 file [Done] Create a new Azure Scheduler Job Collection [Proven Concept] Create a new Azure Scheduler Job that triggers the WebJob The Azure Management Portal provides a nice UI for this functionality, which under the

How can I keep my Azure WebJob running without “Always On”

五迷三道 提交于 2019-11-28 07:02:07
I have a continous webjob associated with a website and I am running that website on the Shared mode . I don't want to go to Always On option as there is no real need for my application. I only want to process the message when the calls are made to my website. My issue is that the job keeps stopping after few minutes even though I am continuously calling a dummy keep alive method on my website at every 5 minute that posts a message to the queue that is monitored by that webjob. My webjob is a simple console application built using the WebJob SDK that has a code like this JobHost host = new

How do I write to the logs in Azure WebJobs from a C# console app?

限于喜欢 提交于 2019-11-28 05:39:58
I'm testing out Azure Webjobs. I wrote a console application which polls a SQL database for new work and processes it. I'm not using the WebJobs SDK because it only supports Azure Storage. I upload the job, it runs, and then it fails with a exception that says it wasn't able to connect to the SQL Database instance. I'm wondering what connection string is being used; is it getting the connection string from the Azure Website. The logs give me this: [03/14/2014 22:24:25 > 512206: SYS INFO] Status changed to Running [03/14/2014 22:24:40 > 512206: ERR ] [03/14/2014 22:24:40 > 512206: ERR ]

Relevant dependencies (DLL) not being copied when deploying using Visual Studio 2013

こ雲淡風輕ζ 提交于 2019-11-28 05:11:29
问题 In one of the webjobs I'm deploying, I'm referencing one of my class libraries (Core) that is taking care of running some process (in this case sending an email using SendGrid). When I deployed my webjobs manually (uploading .zip file) everything worked fine. I cleaned up the deployment and re-deployed using Visual Studio 2013 and the webjob started to have problems. The main issue here is that it's looking for the SendGrid dll that's referenced by my Core class library and not my Console app

Process a file using Azure Function

此生再无相见时 提交于 2019-11-28 04:36:44
问题 I would like to process an input file and output it to some location for ex. FTP or Azure storage. I am trying to use Azure Function with SaasFile input/output. I am getting below error: 2016-07-14T00:44:53 Welcome, you are now connected to log-streaming service. 2016-07-14T00:45:00.580 Script for function 'HttpTriggerCSharp1' changed. Reloading. 2016-07-14T00:45:00.580 Compiling function script. 2016-07-14T00:45:00.721 run.csx(24,25): error CS0622: Can only use array initializer expressions

What happens to “in-progress” jobs when you deploy a webjob?

萝らか妹 提交于 2019-11-28 04:18:00
问题 Subject says it all really :) Say I've got a pretty busy Azure continuous webjob that is processing from an azure Queue: public static void ProcessQueue([QueueTrigger("trigger")] Info info) { .... } If I re-deploy the webjob, I can see that any currently executing job seems to be aborted (I see a "Never Finished" status). Is that job replayed after I release or is it lost forever? Also, is there a nice way to make sure that no jobs are running when we deploy webjobs, or is it up to the

Cannot bind parameter 'log' to type TraceWriter

醉酒当歌 提交于 2019-11-28 03:50:05
问题 Getting the below message when doing right click project -> Debug -> Start New Instance. [1/7/2018 6:48:54 AM] A ScriptHost error has occurred[1/7/2018 6:48:54 AM] Executed HTTP request: { [1/7/2018 6:48:54 AM] Microsoft.Azure.WebJobs.Host: Error indexing method 'TestFilesIngestJobs.RunScheduleAsync'. Microsoft.Azure.WebJobs.Host: Cannot bind parameter 'log' to type TraceWriter. Make sure the parameter Type is supported by the binding. If you're using binding extensions (e.g. ServiceBus,

Initiate a message from bot to user on BotFramework

余生颓废 提交于 2019-11-27 22:17:45
I have a bot built on BotFramework 3.5 and hosted on Azure as a WebApp. I didn't face any problems with implementation of scenarios where the bot needs to respond to user's input. However there is a need to teach him to start conversations by some schedule. To reach the goal I created a WebJob which is a simple console app basically. Here is a code used to initiate a message from bot to user: var botAccount = new ChannelAccount(id: from); var userAccount = new ChannelAccount(id: to); var conversation = new ConversationAccount(false, conversationId); var connector = new ConnectorClient

Azure WebJob in .NET Core

假如想象 提交于 2019-11-27 22:03:32
问题 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. 回答1: 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)