Explains why the current NCover is worth purchasing and using over the old free version. Shows how to use the GUI as well as the console interfaces.
This is partly for my future reference, and partly to share the details. If you’re reading this, you’ll likely know that .NET 4 was released almost two months ago. I’ve recently been upgrading my projects to the new framework, and hit a snag with running post-build unit tests via NUnit.
This is the conclusion to my series on reducing code coupling. This installment follows from the previous ones, building on them by introducing the Inversion of Control pattern.
This is a walkthrough in automating Sandcastle to generate API documentation during an automated build process.
This article is about setting a version number for a code build, and a mechanism to maintain a versioning system over time. This can be done in NAnt with some custom targets.
Provides a description of packaging build artifacts in a Zip file using NAnt’s built in functionality. Includes code for a task to do the job.
This is a look at how one coder’s standard NAnt build file for .NET projects has evolved. In this post, a new standard buildfile will be shown, including a number of useful and commonly-used tasks.
The news has been broken: a new beta of Visual Studio 2010 has become available for MSDN subscribers, and will be available for download by the wider public later this week. I am in the latter group, so must wait a while longer! I think I will prepare a virtual machine to install the beta […]
Introduction Previously, I talked a bit about the nature of coupling in code, and the general preference to keep coupling loose where possible. I then showed one way to reduce coupling by using a service locator. There are multiple techniques to reduce coupling – the service locator is one. In this article, I’ll be illustrating […]
The second part of a series that shows how to reduce code coupling. This part discusses the Service Locator.