Host.json in my Azure functions project not working correctly
I have an Azure Function project built on NET6. Function runtime version: 4.x, and this is my host.json
Host.json in my Azure functions project not working correctly
I have an Azure Function project built on NET6. Function runtime version: 4.x, and this is my host.json
How do i run Azure C# Http Trigger Function locally in https with debugging?
I have setup certificates et cetera, and I use this command to start my Functions:
How do i run Azure C# Http Trigger Function locally in https with debugging?
I have setup certs etc, and i have this:
Azure Function Isolated Streaming
With Azure Functions In-Process, streaming is not a problem. But the more modern Isolated mode seems to not work with streaming, or i am doing something wrong. This is what i tried:
Has anyone been able to setup json style logging on Azure Functions?
I’m trying to set up Azure Functions log json logs similar to here. However I haven’t been able to get them to work properly. It seems to ignore any attempts at configuring my azure function this way. I’m using a dotnet-isolated environment
Is there a way to retrieve License Type for user using Azure SDK?
I need to create an Azure function which will return structure:
Azure function refuse to run as .NET isolated worker?
I have an Azure Function in Net 4.8 (stuck to framework due to WCF)
Azure function not detecting connection string
I created an Azure Function app with two functions inside. I get the connection string using this code (and it works when I run it locally):
Http trigger in Aure functions application
I have an Azure functions application performing background jobs for my web site. Some jobs start by demand. To achieve that I use a single HTTP trigger function calling it from web server, providing job details. The function starts a corresponding orchestration and returns a check status response. It works well in test environment but in production some requests fail. Unfortunately I do not know the response code: there is no appropriate logging for now. But I think it could be due to big number of requests.