Continuous Integration

Be Secure and Compliant with GitHub

How do we ensure security after we have deployed our application? This question comes up in many customer engagements. How do we make something secure and how can we ensure we are compliant? Unfortunately, many of these questions arise after the fact. After the application has been built, or even

msbuild

99% of code isn't yours

Your own 1% is under source control, but are you keeping taps on all of the libraries you import each time you do a dotnet restore or npm install?

Continuous Integration

Global DevOps BootCamp 2017

Yesterday we had a blast. It's the only way to describe it. What started with a small idea over beer in Seattle by a few genius minds, ended up catering to 1500 participants workwide learning about Continuous Integration, Delivery and the promise of Containers and Serverless to make it easier

XAML Build

Building a .NET application using the GitUpgradeTemplate.xaml

Today I received a request which I first found strange. A team that migrated to Git, but still wanted to use their TFS 2008 era TFSBuild.proj. After seeing the investment made in that build file, I understood :). So we though to simply use the GitUpgradeTemplate.xaml which is provided

XAML Build

Resharper 8.1 goes gold & Resharper CLI

For those of you who are using Resharper, version 8.1 was just released with Typescript support and better integration with Visual Studio 2013. The full release blog can be found here. With Resharper 8.1 also ships an updated version of the Resharper Commandline Interface. This allows you to

XAML Build

Referencing Public/Private/Reference Assemblies folder from your project

When you're working on Code Analysis Rules, Custom build activities, MSBuild tasks or anything that integrates directly in Team Build or Visual Studio for that matter, you often need to reference assemblies that ship with Visual Studio. These assemblies are usually stored somewhere in the Visual Studio installation path. Now

Team Foundation Server

Things that make your unit tests unreliable

Over the past few months I've come across a lot of Unit Tests that triggered all kinds of crazy corner cases inside mstest. The most interesting observation is that the behavior inside Visual Studio is often different (or doesn't occur) than in Team Build when this happens. This post will

Static Analysis

Have your Custom CodeAnalysis rule integrate properly with Visual Studio

After porting the MSOCAF rules to FxCop 10, I noticed that you can't use the "Suppress in Source" option. Only the option "Suppress in Project suppression file" is available. Another problem with the global suppression is that it isn't scoped to a type or method, basically

Static Analysis

Run MSOCAF in Visual Studio and on the build server

UPDATE (1st of November 2011): I've since uploaded the re-targetted MSOCAF rules to CodePlex and I've applied a few fixes to prevent CodeAnalysis from crashing under certain conditions. They're not part of any official release, but if you just download the solution and build it, you should be on your