The error message got improved with the latest update of the Azure Function CLI. Info: Here you can find the issue on GitHub. I logged this issue on GitHub and got a response that timer triggered functions also require storage to run. The error itself only said: “A ScriptHost error has occurred”, which of course does not say much of what is going on. If you arent using windows, Azurite is an open source Azure storage API compatible server, and it is recommended by Microsoft to use. This blocked me from being able to debug my function. In order to save on development costs, instead of creating cloud resources, we can install the Azure Storage Emulator for development and testing. 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.
#Azure storage emulator download how to#
These days I use Azure Functions quite a lot for automating things. How to list all the files from the Azure storage on the Blazor WebAssembly application The way to download files from Azure using both ASP.NET Core Web API and Blazor WebAssembly applications How to use JavaScript functions to enable download action on the client-side Until the next article.