On a recent project, I was attempting to use Microsoft SQL Server Integration Services (SSIS) to read files from Azure Blob Storage using the Azure Feature Pack for Integration Services. Using the Azure tasks seemed pretty straight forward until I couldn’t get them to work in the Control Flow for my DTS package.
There are several ways to deploy an application to an Azure web app, some of which include deploying via FTP, using the “publish” feature in Visual Studio, and local Git deployments. While I figured-out the first two methods pretty easily, the third option gave me some issues.
Thanks to this tip on StackOverflow, here is how you add Bootstrap IntelliSense to your Visual Studio Code project.
As a programmer, seeing the error message “Object reference not set to an instance of an object” is pretty common and pretty annoying. What’s even more annoying is when you get that error when simply trying to get the latest source code from your Team Foundation Server within Visual Studio, as shown below.
Over the last weekend, our TFS 2013 server decided to stop building projects for no apparent reason. No one had changed any software on the TFS or build controller servers and the only evidence of a problem was the following message in the “Diagnostics” log file for each build:After spending hours searching for solutions to this problem and finding nothing, I finally figured-out the cause of the issue. The primary hard drive on the TFS server (not the build agent) was completely full. After sending a request to our infrastructure team to add more storage to the primary hard drive on the virtual server that hosts our TFS implementation, the builds started working again.