Posts

Showing posts from August, 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

Azure Container Registry Image Scanning With Azure Security Center

Image
Just to recap in the previous blog post we looked into how to secure Azure Container Registry and in this post will see the offering from Azure Security Center. Azure Container Registry (ACR) is a manged, private container registry service in Azure to build, store, and manage container images and artifacts. ACR service based on the open-source Docker Registry 2.0. This post explains, what you get from Azure Security Center in the context of ACR. Image scanning is important for any Docker registry. Vulnerability scanning for images stored in Azure Container Registry is now generally available in Azure Security Center (March 2020). This capability is powered by Qualys and seamlessly integrated into the Azure Security Center. ACR image scanning requires Azure Security Center Standard tier . When you push an image to Container Registry, Security Center automatically scans it, then checks for known vulnerabilities in packages or dependencies defined in the file. Each scan takes approximate

WSL2: Linux on Windows

Image
Windows Subsystem for Linux (WSL) 2 is no longer just for insiders, you can install WSL2 today with Windows 10, Version 2004 , Build 19041 or higher. The Windows Subsystem for Linux lets developers run a Linux environment on Windows like command-line tools, utilities, and applications directly on Windows, unmodified, without the overhead of a traditional virtual machine or dual boot setup.  WSL 2 provides improvements to file system sharing, boot time and allows access to some cool new features for Docker Desktop users. With Docker Desktop running on WSL 2, users can leverage Linux workspaces and avoid having to maintain both Linux and Windows build scripts. In short, now we can have a Linux development environment on Windows. Step 1:  Update Windows 10 to version 2004 or higher To use WSL2, Windows 10 has to be updated to version 2004 (Build 10941) or higher. Once installed or updated check your Windows version by opening the “Run” dialog (Windows key + R) and enter winver. Step 2: T