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. You can test your application against the storage services locally without creating an Azure subscription or incurring any costs. but if i disable emulator through Cloud Project Properties > Development > Start Windows Azure Storage.
This blocked me from being able to debug my function. Use the Azure Storage Emulator for development and testing (deprecated) The Microsoft Azure Storage Emulator is a tool that emulates the Azure Blob, Queue, and Table services for local development purposes. The emulator is csrun.exe and it took some tracking down as Microsoft seem to. When I created my first timer triggered Azure Function locally, I always received ScriptHost errors. It seems that with Azure web role projects, you can configure Visual Studio to auto-launch the Azure Storage emulator, but I don’t think that option is available for regular ASP.NET MVC projects hosted on Azure web sites. 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. net As I'm gearing up to continue my series of posts on the subject of migrating an application to Azure, one of the things that occured to me was that the existing implementation has unit tests. 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. Using the Azure Storage Emulator Tuesday, Octoazure, azure storage, c. These days I use Azure Functions quite a lot for automating things.