Webjobs/Aspnet核心未启动 [英] Webjobs / Aspnet core not being started

问题描述

我已经按照https://blogs.msdn.microsoft.com/azuredev/2018/08/22/webjobs-in-azure-with-net-core-2-1/

关于如何在Azure上发布使用dotnet核心构建的webjobs.我创建了一个run.cmd文件，其中包含"dotnet"文件.命令以及要调用的dll名称.从Azure Pipelines发布后，似乎没有调用run.cmd. (我的消息在队列中，需要由webjobs使用).我还检查了cmd文件的编码，它是没有BOM的UTF8.

我可以从Kudu门户的CMD调用run.cmd，它可以工作，但是我需要它能够自动启动而不是手动触发来启动webjob.有任何线索吗?

---

Thiago Custodio |软件工程师
博客
Twitter
天蓝色的人

解决方案

您好Thiago，如果您部署了本文中描述的示例项目，则唯一需要做的就是将WebJob Type修改为"Continuous"而不是触发"在WebJob的发布"设置上.

触发的WebJob类型将需要手动干预才能启动.

希望获得帮助.

古斯塔沃·洛佩兹(Gustavo Lopez).

Hi,

I've followed the instructions from https://blogs.msdn.microsoft.com/azuredev/2018/08/22/webjobs-in-azure-with-net-core-2-1/

about how to publish a webjobs built with dotnet core on azure. I've created a run.cmd file that contains the "dotnet" command plus the dll name to be invoked. It seems that after my release from Azure Pipelines, the run.cmd is not being called. (I have messages in a queue that need to be consumed by the webjobs). I've also checked the encoding for the cmd file, and it's UTF8 with no BOM. 

I can call the run.cmd from the CMD of the Kudu portal, and it works, but I need it to be automatically rather than a manual trigger to start the webjob. Any clues?

---

Thiago Custodio | Software Engineer
Blog
Twitter
Meu livro de Azure

解决方案

Hello Thiago, if you deployed the sample project described in the article, the only change you need to make is to modify the WebJob Type to "Continuous" instead of "Triggered" on the Publishing settings of your WebJob.

Triggered WebJob Type will required manual intervention to start up.

Hope this help.

Gustavo Lopez.

这篇关于Webjobs/Aspnet核心未启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！