In this tutorial, we are going to see how to create a Docker Image for an ASP.Net MVC4 application. We will containerize the created image, run it locally and test it. For hosting an ASP.Net MVC4 application we need IIS, so we need a Windows Container (IIS doesn’t run on Linux container). To work with Windows Containers, we need either Windows 10 (Anniversary update) or Windows Server 2016. We are going to use Windows Server 2016 Datacenter VM running in Azure as our development environment.
Continuous Integration and Deployment of ASP.Net Core 1.0 Docker Image to Azure Ubuntu Virtual Machine using GitHub and Docker Cloud
In this tutorial, we are going to see how to get continuous integration and continuous deployment of a Docker image created for ASP.Net Core 1.0 Application to an Azure Ubuntu Virtual Machine. We are going to use GitHub as version control repository where our application code along with Docker file resides. We will use Docker Cloud to automatically build images on every code push to the GitHub repository. Finally we will configure Docker cloud to build the latest image and deploy the Docker container to an Azure Ubuntu Virtual Machine.
In this tutorial, we are going to see how to deploy a Docker image created with ASP.Net Core 1.0 Application to an Ubuntu Virtual Machine created in Microsoft Azure Cloud. Docker helps us in creating packages for our application into standard images. These Docker images are ready to be deployed on Docker Containers and can run on any environment.
In this tutorial, we are going to see how to create and deploy a Docker Image for an ASP.Net Core 1.0 Application. At the end of this tutorial we are going to deploy the Docker image to Azure Linux Web App. Docker helps us in creating packages for our application into standard images. These Docker images are ready to be deployed on Docker Containers and can run on any environment. A Docker Image is a read-only template with instructions for creating a Docker container. A Docker Container is the execution environment and it is created from a Docker image.
In this tutorial, We are going to see how to deploy an Azure WebJob which is based out of an .Net Core Console Application using PowerShell. At this point of time there is no built-in support in Visual Studio to deploy .Net Core based application as an Azure WebJob. We can either deploy the WebJob directly at Azure Portal (which is straight forward) or by using PowerShell. We are going to use combination of PowerShell and Azure Cmdlets to deploy the WebJob.
In this tutorial we are going to see how to use .Net Core Console Application as an Azure WebJob. .Net Core Console application is different from traditional .Net framework Console Application in generating the project outputs. Traditional .Net framework Console App generates executable as project output, but .Net Core Console App will generate DLL (library). We have to do little extra work to make .Net Core Console Application work as Azure WebJob.
In this tutorial we are going to see how to create a simple Azure WebJob using a C# console application with parameters. Azure WebJobs are used to run scripts or programs (typically long running) as background processes on Azure Web Apps. WebJobs can be ran in three different ways – Manually triggered, Trigger on a Schedule and continuously trigger. WebJobs are capable of executing different scripts(for example cmd, bat, exe, js, jar, ps1 etc.,).
In this article, I am going to show how to enable AzureWebsite diagnostic logs using PowerShell. An AzureWebsite supports both Web Server logs and custom application logs. We can identify IIS level request and response information using Web Server logs. Using custom application logs, we can write custom trace messages to track the code flow. We are also going to see how to retrieve these logs for a particular AzureWebsite using PowerShell.
In this short tutorial, I am going to narrate step by step process on how to create an AzureWebsite and publish a Visual Studio 2013 ASP.Net MVC Website using Microsoft Azure PowerShell. Even though we can perform the same operations from Azure Management Portal (and also through Visual Studio), we get more flexibility and control while automating deployment and maintenance tasks from PowerShell. One can create simple scripts which can perform end to end deployment activity (a deployment is not just deploying website, it usually involves creating Databases, Users etc.,).
In this jumpstart, I am going to show how to connect to a Azure Subscription from a remote machine using PowerShell. This approach is useful when we are trying to automate Azure related deployment and maintenance activities from remote machines.
In this short jumpstart, I am going to show how to get list of all AzureWebsites Cmdlets from latest Microsoft Azure PowerShell – May 2015 release. This jumpstart is the starting point of series of blog posts which will narrate different automation techniques involved around AzureWebsites. As the first step, we get list of AzureWebsites cmdlets and keep them as a reference.
Being a tech geek, I always find different sources to educate myself with new technical trends. So far I found World Wide Web (blogs, columns, webcasts, podcasts etc.,) as the most preferable medium to maintain consistency in our daily learning activity. Having said that, one cannot find a proper learning path for a given technology very easily over internet. This gap in continuous learning is filled by reading books which suggests and exemplifies a proper learning path. “HDInsight Essentials” by Rajesh Nadipalli is a perfect example which falls in the afore mentioned category.
In this short tutorial, I am going to show how to publish TWO different Visual Studio Web Projects to a single AzureWebsite. At times we might required to separate architecturally our web components to multiple physical Visual Studio projects to address separation of code concerns. Even though we maintain them separately, we have to publish them (or host them) on a single website. I am going to demonstrate step by step process on how to publish multiple projects to a single AzureWebsite and make every web component work as expected.
AlwaysOn feature when enabled on a site, will automatically ping the site at regular intervals to ensure that the AzureWebsite is always up and running, so that app domain or worker process will not be killed due to idleness.
ScottGu recently (yesterday) announced the staged publishing support for Windows AzureWebsites. The concept of staging deployment is not new in Azure world, we have this support from long time for Cloud Services. In Cloud Services, we can simply make a staging deployment and then test it thoroughly to ensure the integrity and new features of new version, once we test the staging deployment we can simply make a swap between staging and production versions. Thus we get new features and changes included in new version into production with a single button click.
Get-AzureRemoteDesktopFile cmdlet can be used to either save the RDP file of an Azure Virtual Machine on to our local system or to launch an remote desktop connection. This cmdlet saves the RDP file for a particular VM role without any problem. But we get “Invalid Connection file specified” error when we use –Launch parameter with this cmdlet.
In this tutorial, I am going to show how Azure Table Storage entities are being protected for their data integrity during concurrent transactions. Table storage entities are using a property called ETag (included for every entity by default) to keep track of version of an entity. When a outdated Etag or an invalid ETag comes along with an update operation, table storage is going to throw an exception “412 – Pre-condition failed”. Table storage entities also provide an option to force update an entity if in case ETag is allotted a value of “*”.
In this tutorial, I am going to show how to quickly configure SQL Server hosted on Azure VM so that it can be accessible from external SQL Server Management Studio. First we add an end point for the VM in a Azure Management portal. As a second step we open that port (of added end point) to the inbound rules of VM firewall. As a next step we enable TCP connections of the SQL Server on VM and restart the SQL Server instance. Finally we enable SQL Authentication (along with Windows Authentication) for SQL Server and create a SQL Login. We then use the created login to access SQL Server from remote SSMS.
In this short gotcha, I am going to show how to use an Azure PowerShell Cmdlet. Save-AzureServiceProjectPackage to generate CSPKG format cloud deployment package. CSPKG is a cloud ready package and can be upload directly to a cloud service either through management portal or through PowerShell. Previously when there is no support (this cmdlet not used to work before Azure PowerShell 0.7.2) for Save-AzureServiceProjectPackage, we were forced to use CSPack to generate the package.
In this quick gotcha, I am going to show how double quotes can create issues which running Apache Hive query using Windows Azure PowerShell Cmdlets. We have Azure cmdlets like New-AzureHDInsightHiveJobDefinition, Start-AzureHDInsightJob etc., which support running hive queries as map reduce jobs in HDInsight. But there will be a format issue when double quotes are included in the query. To bypass the format issues, one cane use Invoke-Hive cmdlet to invoke the same query. This gotcha applies for cmdlets of version 0.7.2.
JumpStart # 31– Create and deploy new Azure Cloud Service using Package (CSPKG) generated by Azure PowerShell
In this short tutorial, we are going to learn how to create new Azure Cloud Service deployments through Windows Azure PowerShell cmdlets. Deployment though PowerShell can be achieved by first creating a package (CSPKG) for the Visual studio project which is intended to be deployed. As a second step we upload the package to a Windows Azure Blob Storage. Finally we create a new Azure Cloud Service and deploy the uploaded package to it.