#azure-functions

If you got the following email from Microsoft Azure: Migrate your .NET apps in Azure Functions to the isolated worker model by 10 November 2026You’re receiving this email because you use the in-process model with .NET applications in Azure Functions. Beginning 10 November 2026, the in-process model for .NET apps in Azure Functions will no longer be supported. To ensure that your apps that use…

#Test our #code with #json in C#

Test Driven Development (TDD) helps you to validate our code but something you need to check some result as json and it is not easy to find an easy way. After a couple of post on Stackoverflow, here I want to show my solution. Here some examples of TDD.

For my company I’m creating an Azure Functions with .NET Core 3.xto generate the invoices. I have to consider different scenarios and I want…

I want to run more than one Azure Function at the same time but each of them on a different port because by default all Azure Functions are starting on port 7071. How can I do that?

Following the Microsoft documentation, I am setting local host port in local.setting.json. The file looks like below:

{ "IsEncrypted": false, "Values": { "AzureWebJobsStorage": "", "AzureWebJobsDashboard": "" }, "Host": { "LocalHttpPort": 7073 } }

When I run/debug the solution, Visual Studio still host the application on default port (7071).

I have checked the bin directory, the local.setting.json file is getting there with above settings. Running Azure Function CLI (func host start) from bin directory correctly read the port number.

I googled a bit and I discovered is in Visual Studio and how it works. The command line takes precedence over the settings file, the problem is that Visual Studio passes an explicit port on the command line.

Then, I have to override this configuration in same way. I think I can play with the property of a project. There are some parameters or arguments I can add or change.

The work around is to go through Project -> Properties -> Debug, then under Application arguments take control of the arguments. You can type 

host start --port 8085 --pause-on-error

Application arguments in the project property

If you are interested in more posts about Azure Functions, follow this link.

The post Run Azure Function on a different port appeared first on PureSourceCode.

Run Azure Function on a different port

I want to run more than one Azure Function at the same time but each of them on a different port because by default all Azure Functions are starting on port 7071. How can I do that?

Following the Microsoft documentation, I am setting local host port in local.setting.json. The file looks like below:

{ "IsEncrypted": false, "Values": { "AzureWebJobsStorage": "", "AzureWebJobsDashboard":…

In the last couple of weeks, I wrote a lot about Azure Functions because companies like this new approach. First, I want to know how add in a Azure Function dependency injection and read the configuration from a file.

I want to use .NET Core 3.x for my function and store some settings in a configuration file. First problem is where this configuration file is saved, on my machine and on Azure.

Then, I have to inject this configuration and other dependencies in some way to the function. We have to write a bit of code now.

Dependency Injection

What I want to do is pretty easy: create a function to return a value from the configuration. Just to complicated the example a bit more, I want to inject an HttpClient so I can add some logs in there.

I want to made a call to retrieve weather information by instantiating an HttpClient then making a call to a REST endpoint, returning the result.

When I consider how we to test this functionality I immediately run into a problem in that we can’t mock this HttpClient so I can test properly my function.

Assuming our Function class is named CheckWeather, lets start off my creating a constructor that accepts some interfaces to be passed in:

public CheckWeather(IHttpClientFactory httpClientFactory, IConfiguration config) { _client = httpClientFactory.CreateClient(); _config = config; _apiKey = _config["WeatherApiKey"]; _stockPriceUrl = $"https://www.weather.co/forecast?symbol={symbol}&apiKey={_apiKey}"; }

In the method above, we accept an IHttpClientFactory and IConfiguration. The body of the method is not relevant for this example.

In a .Net or .Net Core application we’d usually have a startup class where dependencies are registered in a container and accessible when required.

In Azure Functions, we can do the same thing. Create a ‘Startup.cs` class (technically it could be called whatever you like):

[assembly: FunctionsStartup(typeof(Weather.Startup))] namespace Weather { internal class Startup: FunctionsStartup { public Startup() { } public override void Configure(IFunctionsHostBuilder builder) { ... } } }

Three things to notice here are:

The first line which introduces this as a FunctionStartup class

Implementation of the abstract FunctionsStartup which provides an abstract Configure method that we override; and

The implementation override void Configure(IFunctionsHostBuilder builder)where IFunctionHostBuilder is automatically injected in by the framework

Registering the dependencies is now simple within the Configure method:

builder.Services.AddHttpClient(); builder.Services.AddSingleton(configuration);

So, CheckWeather(IHttpClientFactory httpClientFactory, IConfiguration config) will now have the correct dependencies injected.

Configuration

When you initially create your function, you’re provided with a local.settings.json file which you can use to store whatever values you like. This is useful when running in a development machine where you may not want to create environment variables that means switching out of you IDE.

You may also want to check some of these setting’s into source control.

In addition to this, you want to ensure that in a production environment these settings is read out of environment variables.

In other words, when developing you’d like to read keys from some sort of local file but also environment variables when that exists.

var configBuilder = new ConfigurationBuilder() .AddEnvironmentVariables() .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true); IConfiguration configuration = configBuilder.Build();

Running this locally will fail with an error indicating that the settings (from the local file) cant be found. The reason for this is because it doesn’t know where to look for it. Ordinarily, we’d provide this information to the configBuilder through the ExecutionContext:

public static async Task<IActionResult> Run([HttpTrigger(..., *ExecutionContext context*) { var config = new ConfigurationBuilder() .SetBasePath(context.FunctionAppDirectory) ... }

This ExecutionContext is available to our Run function and will be automatically injected however, the same is not true of the Startup class we’ve introduced and the framework will not inject it into our Configure method.

One workaround for this issue is to introduce:

var localRoot = Environment.GetEnvironmentVariable("AzureWebJobsScriptRoot"); var azureRoot = $"{Environment.GetEnvironmentVariable("HOME")}/site/wwwroot"; var actualRoot = localRoot ?? azureRoot; var configBuilder = new ConfigurationBuilder() .SetBasePath(actualRoot)

The complete Startup class now looks like this:

internal class Startup: FunctionsStartup { public Startup() { } public override void Configure(IFunctionsHostBuilder builder) { var localRoot = Environment.GetEnvironmentVariable("AzureWebJobsScriptRoot"); var azureRoot = $"{Environment.GetEnvironmentVariable("HOME")}/site/wwwroot"; var actualRoot = localRoot ?? azureRoot; var configBuilder = new ConfigurationBuilder() .SetBasePath(actualRoot) .AddEnvironmentVariables() .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true); IConfiguration configuration = configBuilder.Build(); builder.Services.AddHttpClient(); builder.Services.AddSingleton(configuration); } }

And our CheckWeatherconstructor will now work by accepting these injected parameters:

public CheckWeather(IHttpClientFactory httpClientFactory, IConfiguration config) { ... }

Finally, I have the Azure Functions with configuration and dependency injection I wanted. For more information there is A Microsoft documentation,

The post Azure Functions with Configuration and Dependency Injection appeared first on PureSourceCode.

Azure Functions with Configuration and Dependency Injection

In the last couple of weeks, I wrote a lot about Azure Functions because companies like this new approach. First, I want to know how add in a Azure Function dependency injection and read the configuration from a file.

I want to use .NET Core 3.x for my function and store some settings in a configuration file. First problem is where this configuration file is saved, on my machine and on Azure.

My Sunday Reading List

Declarative vs Imperative

https://en.wikipedia.org/wiki/Declarative_programming https://en.wikipedia.org/wiki/Imperative_programming

This is probably your interview questions, even though not many company I came across has asked these. Declarative programming vs imperative programming, is basically, in its very simple form, like functional programming vs object-oriented programming.