Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

If you are a Developer/Architect using Visual Studio as IDE for your development activities, this blog post will be of your interest. During the Ignite 2021 conference, Microsoft released Visual Studio 2019 v16.9 and v16.10 Preview 1. As part of version 16.10 Preview 1, one of the cool features they introduced is to "Remove Unused References..." for any Projects and Nuget packages that are not in use. At the time of writing this blog post, we have Visual Studio Version 16.10.0 (official release) which includes this new feature.  As part of development, we generally get carried away and introduce new Nuget package references to your project and add new references to your Projects. By the end of development, you will not be 100% sure which are not being referenced and unused which means you will leave those unused project references in your application. Now you might be wondering what's the big deal in it since it doesn't harm. The advantage of removing unused project r
Post a Comment

Azure Function v3 with DI (Dependency Injection)

Azure Functions allows you to run small pieces of code (called "functions") without worrying about application infrastructure. Few key benefits of Azure function usage are like Serverless applications we can develop using Azure Function, can develop application with several languages like C#, Java, Python, Powershell. It supports pay per pricing model,integration with several Azure Services etc.

As of today, Azure Functions 3.0 is now go-live and ready for production.One of the major benefits of this release is Azure Functions v3 targeting netcoreapp3.1. If you want to develop using .NET Core 3.1, you must use Visual Studio 2019 16.4 or newer.Upgrading a v2 app to v3 can be found here

Just a brief history about version of Azure function with .NET frameworks
  1. Azure Function v1 - .NET framework 4.61
  2. Azure Function v2 - .NET Core app 2.1
  3. Azure Function v3 - .NET Core app 3.1
Support for dependency injection begins with Azure Functions 2.x. Having Dependency Injection eases things like DBContext, Http client usage (Httpclienfactory), Iloggerfactory, cache support etc.

In-spite of having latest version of Azure function v3 for Dependency Injection to enable few steps are manual as shown below. Hope coming release will incorporate changes or support for the same.

Prerequisites

Before you can use dependency injection, you must install the following NuGet packages:
  • Microsoft.Azure.Functions.Extensions
  • Microsoft.NET.Sdk.Functions


1. Open Visual Studio and select to create a new Azure Functions project ensure you choose v3.


2. To support DI following task need to be done manually.Create the Startup class
  • Configure(IFunctionsHostBuilder builder) method is where we register all services. IFunctionHostBuilder.Services is the IoC Container
  • The Startup class must extend the FunctionsStartup class
  • Registering services is exactly the same way we do in other .NET Core applications by using AddScoped, AddSingleton or AddTransient methods 
3. Removal of Static keyword in Function class and method level


References

Comments

Post a Comment

Popular posts from this blog

Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

Image
If you are a Developer/Architect using Visual Studio as IDE for your development activities, this blog post will be of your interest. During the Ignite 2021 conference, Microsoft released Visual Studio 2019 v16.9 and v16.10 Preview 1. As part of version 16.10 Preview 1, one of the cool features they introduced is to "Remove Unused References..." for any Projects and Nuget packages that are not in use. At the time of writing this blog post, we have Visual Studio Version 16.10.0 (official release) which includes this new feature.  As part of development, we generally get carried away and introduce new Nuget package references to your project and add new references to your Projects. By the end of development, you will not be 100% sure which are not being referenced and unused which means you will leave those unused project references in your application. Now you might be wondering what's the big deal in it since it doesn't harm. The advantage of removing unused project r
Read more

Swagger UI for Azure Function v2 & v3 APIs

Image
In this blog post, we will see how to setup Swagger UI for Azure Function APIs in v2 and v3. Now you might be wondering why Swagger? Swagger is a language-agnostic specification for describing REST APIs, it also referred to as OpenAPI. Swagger UI offers a web-based UI that provides information about your REST APIs service. Prerequisites HTTP trigger Azure function provisioned or created in C# Azure DI enabled on Azure Function, for more details refer here  with relevant package version installed based on Azure Function version. Integrating Swagger UI into our Applications 1. Install the appropriate package based on the Azure Function version which you are dealing with from the below table. Unfortunately, it's not a single package for both versions due to Azure function v3 because v3 makes use of ASP.NET Core 3.1 which introduces a new serializer System.Text.Json (STJ) out-of-the-box.  Azure Function Version  Nuget package  v2               AzureFunctions.Extensions.Swashbuckle  v3
Read more

Authenticate Azure Functions - API Keys

Image
In this blog post, we will see one of the ways to secure your Azure Functions using API keys. Security plays a key role as part of SDLC (Software Development Life Cycle) doesn't matter whether it's exposed to the client/public or even if it's internal. There are multiple ways to secure your Azure Functions like API Keys, Certificate,  API Mgmt, App Service Authentication, etc. If you are new to the Cloud and Azure Functions but want to make a start with minimal effort and less setup of Infrastructure, then API Keys is the ideal choice. Azure Functions allows you to secure HTTP-triggered functions by API access key in the request. As part of creating new Azure Functions, we can select the Authorization Level enum value. If we set the Authorisation level to  Anonymous,  no security applied which means no authentication applied for the endpoint. Authorization Level - Function By setting the Authorisation level to Function each Azure Functions require a specific API key to Auth
Read more