The error message got improved with the latest update of the Azure Function CLI. Info: Here you can find the issue on GitHub. The emulator provides cross-platform support on Windows, Linux, and macOS. When youre satisfied with how your application is working locally, switch to using an Azure Storage account in the cloud. I logged this issue on GitHub and got a response that timer triggered functions also require storage to run. The Azurite open-source emulator provides a free local environment for testing your Azure blob, queue storage, and table storage applications. The error itself only said: “A ScriptHost error has occurred”, which of course does not say much of what is going on.
NET) via the Web Platform Installer, available at.
This blocked me from being able to debug my function. This edition is free of charge and can be downloaded and installed (including the Windows Azure SDK for. When I created my first timer triggered Azure Function locally, I always received ScriptHost errors. As I love to work with Visual Studio Code and Node.js, I choose to use the Azure Functions CLI. It is up to you to choose which one you want to use. Visual Studio Tools for Azure Functions: Right now, you have the following options: Azure Functions CLI, Visual Studio Tools for Azure Functions or use the Serverless Framework. Since the general availability of Azure Functions which was announcement back in November 2016, they are becoming even more popular and are being used for various kinds of things.Įven the local development process of Azure Functions got a lot better. These days I use Azure Functions quite a lot for automating things.
0 kommentar(er)
