This is the final part of the series about building an ASP .Net Core Web Application and deploying it as a Docker container using Microsoft Azure. Here, we are going to set up a Microsoft Azure DevOps release pipeline to automate the deployment of our application as a container on Azure Web App Service. If you have been following along, you should have: a GitHub repository with an ASP .
This is the second article in the series. We are going to set up a Microsoft Azure DevOps build pipeline to automate the tasks we did manually in the first article of the series. Each time we push a change to the master branch, the build will be triggered to build our application, then build a Docker image and push it to Docker Hub. If you have been following along, you should have:
Do you often ask yourself: I have built an ASP .Net Core Web Application, now what? How do I take it to next level using tools/platforms like GitHub, Docker, CI/CD and Microsoft Azure with my application? If YES!! You are at the right place! Introduction This article is the first in the series where we are going to: - build a simple ASP .Net Core web application - containerize it with Docker and run it on local host - push everything to GitHub for later use
The relationship between objects defines how these objects will interact or collaborate to perform an operation in an application. In any application, objects of user interface classes interact with the business layer objects in order to perform an operation. And in the background, the business layer objects may interact with objects of some repository which in turn talks to some data source object or service object. Case Study Before we go ahead, let’s consider a Customer Order Management application that manages the orders placed by its customers for some products.
Code reusability has always been one of the major concerns for software developers. You do not ever want to write a similar code for two business problems. You would rather like to write the solution once and reuse it whenever and wherever required. This requirement of code reusability gave rise to the concept of creating assemblies and using them in different applications by adding a reference to the same. We will get to know more about it as we have a closer look at assemblies.
It has been quite a long time since var was introduced, yet it stands debatable among .Net developers. Everyone has a different understanding as and when to use var as a type. A couple of days ago I was also a part of one such discussion, and so I decided to share my understanding. Readability Every developer has all the right to use var as and when they like, it’s just a matter of one’s choice.
Copyright (c) 2021, Gaurav Gahlot; All Rights Reserved.
Template by Bootstrapious. Ported to Hugo by DevCows.
