Signing Windows executables and Visual Studio Team Services

When you download a program from the internet and execute it, User Account Control warns you about the application you’re about going to start. When you start the Firefox installer, for example, you get a message like this:

Windows tells you who the publisher of this file is. In this case, it’s the Mozilla Corporation. In this way, it warns users who download a certain file, who the original publisher is. If the file has been tampered, the publisher will be reset into an “Unidentified Publisher”.

Visual Studio Team Services (VSTS) has build in tasks to sign iOS and Android applications, however there are no off the shelf solutions for signing Windows applications. ThereforeĀ I investigated a way for signing an application within VSTS using Continuous Integration.

Read More…

Posted in DevOps at October 24th, 2017. No Comments.

Excluding generated files from source control, include in Visual Studio

Auto generated files you typically don’t want to have under source control. I had this problem when building an Wix installer project, where I gather all files I want to include in my installer via the HeatDirectory task. This generates a file, called for example myfiles.wxs, which I need in my Visual Studio project to compile a valid Microsoft installer. Since the rest of my project depends on this wxs-file I want to include it in my projectfile, but exclude it from source control.

To fix this, I used the following way of working:

Read More…

Posted in DevOps at July 14th, 2017. No Comments.