To simplify the use of our build scripts, and to make it easier for someone new to the project to work out how things work, we’ll create some convenience PowerShell scripts to launch the build. We’ll create three scripts, for three different purposes: one for moment to moment use by a local developer; one to do a release build when the project is ready for distribution; and one for our continuous integration server.
Version numbering is an odd detail - one we can (and should) easily ignore at the start of a project. There comes a point, however, where we find that version numbering is vitally useful. At that point, we usually discover that we should have started versioning things about six months ago … and now we have a mess to clean up.
Perhaps the most significant problem with the simplistic versioning system we put into place last time is that we can get the same version number generated on different branches. Fortunately, semantic versioning gives us room to fix this by adding a descriptive suffix to the build number.
Monday, September 18 2017 sharpen-the-saw
In this edition: The Single Responsibility Principle; keeping a log in notepad; Visual Studio 2015 Update 2 RTM; NCrunch; Killing solid communication; Social engineering; Rejecting stereotypes; and What is agile anyway?
While NuGet provides all the power needed to explicitly control every aspect of a package (something the exacting control freak in me really appreciates), a simple project like this doesn’t need anything more than the standard conventions.
Monday, September 25 2017 sharpen-the-saw
In this edition: Good design for developers; Code Maid for Visual Studio; the key to Productivity; Tattoo friendly companies; and Seven Ineffective Coding Habits of Many Programmers.
Once you have a reasonable suite of unit tests, you might start to wonder how much of your code is properly tested. Measuring coverage gives one perspective, and it’s one we can easily add to our builds.