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

Building a CI pipeline for Containerized Asp.NET Core 3.1 using ACR Registry


This is continuation of a series of posts on using Docker and containerization with .Net Core. If you are new to this series its recommend to look at Getting started with Docker and Containers

In this post will show how to setup a pipeline that continuously builds a repository that contains a Docker file. Every time you change your code and commit, the image is pushed to ACR Registry.

Pre requisites
1.     Github account
2.     Azure DevOps Organisation if you don’t have one, you can create for free
3.     Ensure you’re administrator of the Azure DevOps project
4.     Azure Container Registry – more details can be found here
5.     Azure Project to be created in Azure DevOps
6.     Service Principal created in Azure – Creation process can be found here

Get the code from GitHub
https://tinyurl.com/ydtggef6

Configuring Service Principal for Azure DevOps
1.     Setup service connection in Azure DevOps. Navigate to Project settings à New Service Connection à Azure Resource manager

Populate Service principal details as shown below for setting Azure Service connection


Create the Pipeline
1.     Sign in to your Azure DevOps Organisation and navigate to your project
2.     Go to Pipelines and click on New Pipeline

3.     Select where is your code from the below screen. In our example its on GitHub. If you’re proficient with YAML choose GitHub YAML where your pipeline can be scripted and for new people to start we will be using classic editor which provides GUI interface.



4.     After clicking on Continue it prompts for Built template lets start with empty job template
5.     Navigate to Trigger tab and enable “Continuous Integration” for the respective branch which enables CI on it.


6.     Navigate back to Tasks for adding Docker task in pipeline.
Note: Docker Task version used here is 1.* With 2.* pushing to Registry can be done with One task which is build and push.


7.     Configure Pipeline task
a)     Build Task 
b)     Push Image Task


Save the pipeline, all set to go at this point. Now if we trigger a build or code is pushed to repository, In ACR repository we should be able to see the latest image pushed from Azure DevOps.

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