Thursday, 19 December 2019
Saturday, 14 December 2019
Thursday, 5 December 2019
Sunday, 1 December 2019
Let’s have a look at pictorial representation of the proposed strategy first.
Saturday, 30 November 2019
Tuesday, 26 November 2019
Thursday, 21 November 2019
Thursday, 7 November 2019
Resolving “ERROR: There was a conflict. The remote server returned an error: (403) Forbidden.” While Creating Function App in Azure in IaC
Monday, 28 October 2019
To add rollup columns in Azure Boards, navigate to Backlog section and select a backlog level such as User Stories backlog. Then click on Column Options.
Monday, 14 October 2019
Wednesday, 25 September 2019
Wednesday, 18 September 2019
Saturday, 31 August 2019
Sunday, 25 August 2019
We have discussed how to build a .NET Core 3 Web Application in the previous post. In order to deploy a .NET Core 3.0 Web App to an Azure Web App, you need to install .NET Core 3.0 Extension to the Azure Web App. You can easily add .NET Core 3.0 via Azure Portal to a Web APP. However, if you are really into automating your infrastructure as code (IaC) you may want to make all these steps automated and executed via a deployment pipeline. Let’s look at a script which is using Azure CLI and Azure PowerShell to fully automate creation of a .NET Core 3.0 enabled Azure Web App.
You can download the full script from here. Let’s understand each part of the script.
Thursday, 1 August 2019
Sunday, 28 July 2019
Saturday, 27 July 2019
Resolving 'NoneType' object has no attribute 'azure_services' While Setting a Network Rule to Azure Key Vault
Sunday, 7 July 2019
Wednesday, 22 May 2019
Saturday, 18 May 2019
Thursday, 9 May 2019
Thursday, 11 April 2019
The script available here can be used for this purpose. A slightly modified version of the script to support release pipeline and enable sending any variable name and value for updating a value of a given variable can be found here.
Monday, 25 February 2019
Thursday, 31 January 2019
Wednesday, 30 January 2019
Sunday, 6 January 2019
Deploying ASP.NET Core App to Azure Kubernetes Services (AKS)–Setting Up Azure DevOps Pipeline Manually–Step By Step Guide–Part 2
In the part 1 of this post, enabling Docker support for ASP.NET Core app and building and pushing the Docker image to Azure Container Service, using Azure DevOps build pipeline with simple steps was described. The image is tagged with the build Id and it is pushed to the Azure Container Registry, so that it can be later deployed to a container orchestrator to run the container. Helm is used to get he deployment done to AKS via Azure DevOps when creating a an ASP.NET Core App, Container Registry and AKS, then getting it deployed automatically with few clicks using Azure Projects as described in the post “Deploy ASP.NET Core App to AKS with Azure DevOps Project”. Let’s look at getting the container image in Azure Container Registry deployed to AKS with three simple steps without using Helm, with Azure Pipelines.
SQL Server Integration Services (SSIS) projects can be created to perform ETL (Extract Transform and Load) operations. As Implementing of Co...
Task groups are really useful to share common actions with multiple build or release pipelines in Azure DevOps (VSTS). You can group multip...
You can easily clone a build and create a new build definition in the same team project. This is useful when you have similar type of applic...
Pull Request are the controlled way to bring in the changes to your stable branches in your Azure Git repos, or for that matter all Git prov...
Adding Azure Subscription to Azure DevOps as service connection is really simple when you have the same account you are using for Azure Dev...