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

Getting started with Docker and Containers

This is the first part of a series of posts on using Docker and containerization with .Net Core

 Background
Docker, the technology which is nothing but a tool designed to make it easier to create, deploy, and run applications by using containers. A suite of command-line tools for creating, running, and sharing containers.

Containers in simple words are nothing but fast light weight virtual machines (conceptually). Containers allow a developer to package up an application with all of the parts it needs, such as libraries and other dependencies, and ship it all out as one package. Containers offer a logical packaging mechanism in which applications can be abstracted from the environment in which they actually run. Available for both Linux- and Windows-based applications.

Containers and Virtual Machine
We often get asked how Containers are different from Virtual Machine? Are they same or is it VM++?


Virtual Machine vs Containers
  
Containers and virtual machines are two ways to deploy multiple, isolated services on a single platform. As we can see in the above figure if we are running each an application in Virtual machine it needs to have its own Operating system using hardware VM support. VMs are an infrastructure level construct to turn one machine into many servers

The container’s system requires an underlying operating system that provides the basic services to all of the containerized applications using virtual-memory support for isolation. Containers are an app level construct

Benefits of Containers
·       Reduced IT management resources, less OS overhead with improved VM density
·       Reduced size of snapshots (Lightweight)
·       Quicker spinning up apps (Speed)
·       All containers share the host OS
·       OS level virtualization
·       Ability to keep apps isolated not only from each other but also from their underlying system
·       Portability - You can readily move container-based apps from systems to cloud environments or from developers’ laptops to servers if the target system supports Docker
·       Containerized software will always run the same, regardless of the infrastructure.

Containers run everywhere
Containers run anywhere, easing the development and deployment of applications. Windows, Mac, Linux, datacenters, cloud and even IoT.


Use case for Containerisation
  1. Containers Enable Hybrid and Multi-Cloud Adoption
    2. Once containerized, applications can be deployed on any infrastructure – on virtual machines, on bare metal, and on various public clouds running different hypervisors.
  2. Containers save on VM licensing
  3. Better utilization of hardware resource if it’s under utilized
  4. Reliability from one computer environment to another
  5. Microservices model of application design



Comments

swapnil.kolhapur said…
Good one Raju... Next write something about kubernettics
9 December 2019 at 08:57
Raju RH said…
Thanks Swapnil sure it's in pipeline once finished with Containerisation series. will keep you posted
9 December 2019 at 22:13

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