我有一些 C# Azure Functions 使用 定时器触发器.我已经将它们设置为这样,其中 %TimerSchedule%
指的是应用程序设置中的 cron 表达式:
I have a few C# Azure Functions that run on a schedule using timer triggers. I've set them up like so, where %TimerSchedule%
refers to a cron expression in the app settings:
public static void Run([TimerTrigger("%TimerSchedule%")]TimerInfo myTimer, TraceWriter log)
在开发过程中,我经常想使用 Azure Functions Tools for Visual Studio + Azure Functions Core Tools 在本地运行函数.但是当我按 F5 在本地调试该功能时,它(通常)不会立即运行.相反,它会根据计时器计划开始等待下一次发生.例如,如果我的 cron 表达式说每天晚上 8 点运行,我必须等到晚上 8 点才能在我的机器上实际运行该函数.
During development, I often want to run the functions locally using Azure Functions Tools for Visual Studio + Azure Functions Core Tools. But when I hit F5 to debug the function locally it (usually) doesn't run immediately. Instead, it starts waiting for the next occurrence as per the timer schedule. So for example, if my cron expression says to run daily at 8PM, I'd have to wait until 8PM for the function to actually run on my machine.
所以我的问题是:让函数在本地运行一次的最简单和最好的方法是什么?
我尝试过或考虑过的事情:
Things I have tried or considered:
Run()
提供 TimerInfo
和 TraceWriter
参数——我发现令人惊讶的是,这方面的文档很少.TimerInfo
and TraceWriter
arguments to Run()
– and I've found surprisingly little documentation for that. Microsoft 的 在 Azure 中测试代码的策略函数 页面在这个主题上不是很有帮助——它只提到计时器触发器作为测试其他触发器类型的一种方式.
Microsoft's Strategies for testing your code in Azure Functions page is not very helpful on this topic – it only mentions timer triggers as a way to test other trigger types.
在理想情况下,我按下 F5,该函数会立即运行一次 - 就像开发普通".NET 应用程序一样.
In a perfect world, I'd hit F5 and the function would immediately run once – just like developing a "normal" .NET app.
我有同样的问题,并使用 DEBUG-flag 仅在调试时拥有 RunOnStartup:
I had the same question, and used the DEBUG-flag to have the RunOnStartup only while debugging:
public static void Run(
[TimerTrigger("* 0 7 * * 1-5"
#if DEBUG
, RunOnStartup=true
#endif
)]TimerInfo myTimer, TraceWriter log)
{
这篇关于在本地运行一次计时器触发的 Azure 函数的最简单方法是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!