Raju RH

This is continuation of a series of posts on using Docker and containerization with .Net Core. If you are new to this series its recommended to look at Getting started with Docker and Containers .  . NET Core 3.1 released  December 3, 2019 as a Long-term support  release as part of this post we will see how to containerise a Web API type application. Getting Started In this post we are going to see how to build a Container based application and basic commands which we use everyday when working with containers. Prerequisite’s                                                                                         ·        Install Docker         ·        Install .NET Core 3.1 SDK         ·        Visual studio 2019/ Visual studio code         ·        Visual studio extension Docker to be installed from Visual studio marketplace Steps For demo purpose I will be running on Docker Linux container If you are new or first timer for Docker its recommended to use

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 vir

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