Tag Archives: continuous integration

Packaging of a .NET application on Windows

This post is about how to package .NET application for Windows into an MSI (MicroSoft Installer) package using Wix# tool in command line. Packaging process can be easily automated on continues integration server.

msi_package

Generally application building workflow is simple:

  • Assign a version number to an assembly
  • Build binaries
  • Copy binaries to package folder and build msi-package with the same version as  assembly

Build process will be controlled by MSBuild project file and can be started from a continues integrations server.

Sample solution is available for download here https://github.com/mchudinov/PackagingMSI. Solution is compatible with Visual Studio 2013.

Automated building and versioning processes were described in my previous posts:

Continue reading

Packaging of a Mono application on Linux

How to package a Mono (.NET) applications for Debian-based Linux in command line. Packaging process can be easily automated on Continues Integration Server.

debian_package

Package building workflow is quite simple:

  • Assign a version number to a .NET assembly code
  • Build binaries
  • Copy binaries to package folder and build deb-package with the same version as an assembly

Build process will be controlled by MSBuild project file and run from a continues integrations server. MSBuild on Mono platform is substituted by xbuild utility.

Sample solution is available for download here https://github.com/mchudinov/PackagingMono. Solution is compatible with Visual Studio 2012, MonoDevelop/Xamarin Studio 5.

This is my third blogpost about automation of development workflow with Mono. Automated building and versioning were covered in my previous posts:

Continue reading

Versioning of .NET assemblies

I use four-parts version pattern that looks like: {Major}.{Minor}.{Date (MMdd)}.{Build Number}

An example version in this format would look like: 1.7.1028.37, which breaks down into being the first major release, seventh minor release, built on 28 October, and has been the 37th build for v1.7. Every time assembly is rebuild build counter increases.

version1

Sample solution is available for download here https://github.com/mchudinov/Versioning.

Continue reading

Building and testing .NET application in command line

Setup: Windows – .NET 4.5, Linux – Mono 3, Mint 17 (based on Ubuntu 14). I need to build and test .NET application from command line and on CI server.
Sample solution can be downloaded from here https://github.com/mchudinov/BuildingTesting. Solution is compatible with MonoDevelop 5, Xamarin Studio 5 and Visual Studio 2012,2013,2015.

building_bricks

1. Building in command line

There are two standard command line building tools for .NET: MSBuild on Windows and xbuild on Linux/Mono. xbuild build files are compatible (with some exceptions) with MSBuild files.

We need at least 4 simple steps (targets as they called in MSBuild terminology) to build a .NET solution:

  • Clean
  • Restore NuGet packages
  • Build binaries
  • Run unit tests

Continue reading

TeamCity agent on Windows with Git through SSH

How to make work TeamCity Agent  on Windows with Git through SSH

1. Run TeamCity Agent not from System account

2. This account must have a PuTTY session stored with SSH key

3. Server’s key must be cached by the TeamCity agent acount. Run plink in console and point plink to the target server.

Confirm key caching ‘y’

Integration between issue tracking system, CI server and VCS. Part 3 resolve an issue

This is the third part of my blogpost about integration between issue tracking system, CI server and VCS. Part 1 is about components setup. Part 2 is about project setup.
Continue reading

Integration between issue tracking system, CI server and VCS. Part 2 project setup

This is the second part of blogpost about integration between issue tracking system, CI server and VCS. Part 1 is about components setup. Part 3 is about resolving an issue.
Continue reading

Integration between issue tracking system, CI server and VCS. Part 1 components

This is the first part of my blogpost about integration between issue tracking system, CI server and VCS. Part 2 is about project setup. Part 3 is about resolving an issue.
Continue reading

A Maturity Model for Continuous Delivery

Here is an interesting rough systematization in a table view of Continuous Delivery process. It is composed by Sveinung Dalatun and Stein Inge Morisbak employees of a Norwegian company named Bekk. They called this table A Maturity Model for Continuous Delivery. This model was published once in a Norwegian paper magazine called “The Developer” number 3 year 2013. There is a short description-article following the Model published in The Developer. The are Some quite interesting thoughts there.
Continue reading