Posts

Showing posts from February, 2020

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

Application Insights – Azure Service

Image
Application Insights is an Azure Service which helps to monitor applications in real time. It’s a powerful service for Developer and DevOps professional which provide insights of your applications in terms of Performance, Application Health, Application Interaction, User flows, Availability, and its live metrics. Application Insights works on applications hosted on-premises, hybrid or any other cloud service provider. Application Insights comes with capability like Querying the metrics, dashboard for representing different metrics, ability to configure alerts, Integrating with Azure DevOps etc. Application Insights can be used for monitoring Azure Services like Azure App service, VMs, Azure Function etc. Similarly, if you have existing application already build or deployed you can easily configure application-based monitoring using Application Insights SDK. We will see below how easy to integrate with new or existing application. Below are the steps involved in configuring Ap

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

Image
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  à  N