Posts

Showing posts from October, 2019

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 WebJob using .NET Core

Image
Background WebJobs is a feature of  Azure App Service  that enables you to run a program or script in the same context as a web app, API app, or mobile app. There is no additional cost to use WebJobs if you are running under the existing web app. WebJobs is not something new to Azure or .NET , there’s even a default Azure WebJob template in VS 2017 but for .NET framework. No VS template exists for Azure WebJob in .NET Core but that doesn’t stop us using .NET Core for WebJob. Creating WebJob in .NET Core is not hard but need to incorporate certain tweaks using HostBuilder and WebJobs SDK version 3.x. I have tried to incorporate end to end process with sample code snippet for Timer Trigger using .NET Core. .NET Core with WebJobs SDK versions 3.x Version 3. x  adds support for .NET Core. Visual Studio tooling for .NET Core (3. x ) projects differs from tooling for .NET Framework (2. x ) projects. With 2.x you can still implement in .NET Core but with 3.x it simplifies and we ca