Global Azure Boot Camp 2018, Austin TX

Here are the recorded sessions of GAB 2018. All sessions are recorded at which was founded by Shawn Weisfeld (Cloud Architect from Microsoft) in January 2011 with a mission to provide user group content online for free. Check out more at

Azure in 60 minutes – by Shawn Weisfeld


Microservices , Containers, Devops and Kubernetes in Azure Cloud – by Eddie Vallalba


Azure SQL Database: Where Does My Data Belong? – by John Sterrett


An Introduction to Blockchain on Azure – by Sucharit Reddy


Getting Hands-on with Azure Logic Apps – by Stephen W.Thomas


The Domain Model of Continuous Delivery – by Jeffrey Palermo


Fix : Error compiling for board SparkFun ESP8266 Thing Dev

Recently I was trying to setup Arduino with my newly brought SparkFun Thing Dev Board and surprisingly I had been facing a strange issue while compiling it which states

open C:\Users\{username}\AppData\Local\Temp\arduino_build_773581\sketch\app.ino.cpp: The process cannot access the file because it is being used by another process.
Error compiling for board SparkFun ESP8266 Thing Dev.


Based on every details provided in I found that there were no issues while configuring Board, Port and libraries required to compile it. Spending almost two sleepless nights, I almost gave up to find a resolution for the issue I was facing.

Every time I am opening the Arduino board and compiling the app.ino.cpp file which was located in a different directory, this file was getting generated in Temp directory. Seems to me a permission issue but being an administrator, I was surprised to get this issue again and again.

Finally, I found the resolution which was so simple to do.

Get to the environment variables of the system and change the value of TEMP and TMP variable to C:\Temp instead of %USERPROFILE%\AppData\Local\Temp.



That’s it, everything started working as expected. Complied successfully and then uploaded it to the board without any issue. Hope this helps for someone who is facing similar issue

Global Azure Boot Camp 2017, Austin TX

Here are some of the boot camp session and training videos from Global Azure Boot Camp 2017 that was held in Austin, Texas.  Thanks to my friend Shawn Weisfeld @Technical Evangelist at Microsoft who had helped me to organize this boot camp at Microsoft campus along with an awesome setup of streaming and recording this videos at Shawn is the founder of

Also my sincere thanks and gratitude to our local sponsors and contributor Clear Measure, Austin .NET User Group and my organization Sogeti USA LLC for helping me organize this event with eminent speakers, foods and beverages along with Microsoft global organizers.

Mostly I am thankful to the following eminent speakers and contributors for this boot camp

2017 Austin Global Azure Boot Camp Welcome Note



Azure Foundation



Making the Case for the ServiceBus



Making Teams Fly with Continuous Delivery to Azure



Introduction to Azure Security Center



Building Powerful intelligence using Cognitive Services



Big Data in Azure



2017 Austin Global Azure Bootcamp Closing Note



Enjoy the videos and happy Azure Learning

Build and Deploy Web Application and Web API as Azure Web App through VSO Continuous Integration

I thought to write this post which might help my fellow developers to know how to create a CI build for any web application or web API through Team Services of VSO. Just like in one of the post I have explained how we can create a NuGet package using CI build, this post might give more insight about building and deploying an web application directly to Azure using CI build. Let’s get through the steps involved.

Step 1: Install and configure Azure PowerShell

This step is highly important if you don’t have Azure PowerShell installed. The cmdlets of Azure PowerShell can be used to create/configure cloud apps/services, VM, virtual networks, etc. Download an install Azure PowerShell from this link.

Once installed open Windows PowerShell in administrative mode and run the following Azure PowerShell cmdlets to get details of your Azure subscription and resources available. Main that you need is your Subscription Name and Subscription Id.

Command to get Azure Account Information: Login-AzureRmAccount


Command to get Azure Resources available: Get-AzureRmResource

Command to get the Subscription Name and Id: Get-AzureRmSubscription

Command to get the Azure Publish Settings File: Get-AzurePublishSettingsFile

This command is important to get profile settings for publishing your web app in Azure. This will download the publish settings file along with the credentials in your local box.


Step 2: Create New Service Endpoint in Team Services dashboard

This step will help us to register or add our Azure subscription to TFS. This is done only once and at collection level using the Service tab. Just select New Service Endpoint and select Azure Classic.


In Add New Azure Classic Connection choose Subscription Id and Subscription Name that you got from Azure Command Get-AzureRmSubscription. The Connection Name can be based on your preferred one. You can even open the downloaded Publish Settings file to get the Subscription Id and Subscription Name. Also from the file, copy the content of Management Certificate and paste it in place holder as shown below while creating the new Connection.


Now this service endpoint is ready to be used while publishing the azure web app.

Step 3: Configure the Build and Deployment properties of Team Project

Create the build definition file for the team project for which you want to instantiate the CI build at every check in process to source control. For that select Azure WebApp from the Deployment tab of Build Definition window.


As usual in Build definition created, update your Mapping information to point to source control repository of your solution in Repository Tab. Update your CI filter in Trigger tab to point to source control repository of your solution.

Next lets select the Build tab and select Azure Deployment. In details section, you need to select the new service endpoint created and select the Web App Name.


That’s all we need. Now you can queue the build to see how it works.