Ok, this should be the last post about speaking engagements for a while ;) I have something else in the works that’s going to take a lot of my attention for some time (more on that on Friday).
I’m pleased to announce that I’ll be returning to Fort Wayne in June to talk about the Microsoft Fakes framework (formerly the Moles framework). In this talk I’ll introduce the Fakes framework, discuss the use cases for the different isolation techniques, and show how to take advantage of them in your unit tests.
The meeting will be held on Tuesday, June 12 at the Northeast Indiana Innovation Center. Pizza and drinks will be available at 6:00 with the presentation starting at 6:30. For more information please check the NUFW site.
I’ve been using TortoiseSVN for years. One place I’ve found it lacking in the past though was when I wanted to remove unversioned files from my working copy. This has generally been a nuisance but I’ve dealt with it. A few days ago, I needed to recover from a merge gone wrong and got serious about finding a better way.
It’s the second week of February so if you read this blog with any frequency you know what that means. That’s right, IndyNDA is this Thursday (9 February)! This month we’re fortunate to have Phil Japikse returning to discuss testing legacy code.
Michael Feathers defines Legacy Code as any code that doesn’t have automated tests, and you agree that automated tests are an important facet of successful software development. Then it happens – you get your next assignment, and it’s your worst nightmare! You have to maintain and enhance a large application that has no tests in place, and there are parts that are just plain scary. Where do you start? Traditional Test Driven Development techniques don’t typically work, since they focus on an inside-out development paradigm.
I will show you the patterns and practices that will help you turn the scary big ball of mud into a tested code base.
I’m excited to have Phil back. I’ve heard him speak many times and have always found his talks both informative and entertaining.
This month we’re meeting in the 2nd floor conference room at 900 E. 96th Street. Registration begins at 5:30 and the main event kicks off at 6:00. Snacks and soft drinks will be provided.
A few nights ago I was over at my local Fry’s looking for a battery charger and a new Compact Flash card for my camera when I stumbled upon the book Driving Technical Change by Terrance Ryan. I think it was the distinctive look of a Pragmatic Bookshelf title that caught my eye. I picked it up, glanced over a few pages, said “what the hell,” and bought it. The book weighs in a bit under 150 pages so it’s a pretty quick read. Even with my slow reading pace and note taking I managed to make it through the book in just a few hours.
3/27/2012 Update: According to the Moles page, the Moles framework has been integrated into Visual Studio 11 as the Fakes framework and Moles is no longer under active development. After a quick review of the changes it appears that most of this guide still applies but there are a few changes to be aware of:
Mole types are now referred to as Shim types
The configuration file now has a .fakes extension
The generated types are now placed in a .Fakes namespace (i.e.: System.Fakes)
6/25/2012 Update: In preparation for my Faking It talk covering the Fakes framework I compiled a list of the notable differences between Moles and Fakes. There are quite a few more than I listed above so if you’re using this post as an introduction to either framework you’ll probably want to look them over.
Despite having been around for several years I hadn’t heard about Microsoft’s Moles framework until a few months ago when one of my teammates mentioned it during the 2011 Indy GiveCamp. I was interested in learning more about it at the time but given how we were running on caffeine I’m not surprised I forgot about it until he mentioned it again a few weeks ago. This time I was much more alert and started reading about it almost immediately. After seeing what Moles offered and not finding much in the way of resources for it on the Web I knew I needed to spread the word.
Recently I’ve been working with a third party component vendor to resolve a defect. They requested that I create a sample project illustrating the issue and send it to them as a zip archive. Building the project was easy but I didn’t want to send all of the extra stuff that goes along with it. In other words, I wanted a snapshot of the current revision but without the source control bindings. I knew how to do this with Subversion but how did Mercurial handle it?
Since I started using Mercurial a few months ago I’ve fallen in love with it. There was a bit of a learning curve for getting up and running but I found that the Tortoise tools are really intuitive and eliminated some of the pain. Most importantly though, Mercurial addresses the single biggest problem I had when working away from home – no repository access.