A recent post provided an introduction to using Composer to manage PHP dependencies. This post is a follow-up which shows how to leverage Composer functionality from within the PhpStorm editor.
Composer is a productivity tool for PHP developers. It provides structure for managing a project’s dependencies, and for packaging a project to be used as a dependency such as a library or framework. This post provides an introduction to Composer, some of its use cases, and usage examples.
I previously wrote about code coverage for automated tests using NCover 1, and then about updating to NCover 3. Now, some years and two major versions later, it’s time to revisit the tool.
NDepend is a commercial tool used to analyze compiled .NET assemblies, and generates resulting metrics, diagrams, and reports. The newest version – NDepend 4 – is available with come notable changes, described within.
I’ll share something I’ve been using to simplify creation of new .NET projects: a base project. It is intended to reduce setup of common directories and tools.
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.