Author Archives: simon

Running node.js on windows now is not that difficult. I cheated and installed some binaries, rather than building from source via cygwin. Here are the steps I took: Download the binaries from http://node-js.prcn.co.cc/. Find the latest “complete” release which was … Continue reading →

Just a quick one, as I just lost an hour on this problem. If you are trying to set up your environment to run with the above environment, you will likely see the following error message when you try and … Continue reading →

One of the nice things about open source software is that sometimes you don’t need to write code you think you need to. I have found that it is possible to generate SpecFlow execution reports with assemblies built against xunit … Continue reading →

I struggled yesterday with saving modified entities back to the database after they were disconnected from their original DataContext. After much googling, I found the way forward is to ensure you have a version column in your database with a … Continue reading →

If you are behind a http proxy, and wanting your application to connect to a REST or Web Service, it is likely you will not be able to, and will get a Http Status code of 407 back. However, you … Continue reading →

Earlier, I mentioned how I was creating an archive copy of a workbook. I found a more efficient way of doing things that works a lot faster, and is a whole lot less code Sub SaveFileWithoutFormulas() If SaveWorkbook Then Dim … Continue reading →

Well, I feeling slightly pleased with myself. Last time, I wrote that I had found it difficult to discover how outputting reports in SpecFlow worked. Well, following Ayende’s motto of “I completely agree, can you send me a patch”, I … Continue reading →

It took me a while to figure out how to generate reports in SpecFlow. After all, now we have all these lovely Specification written and the code written to satisfy our requirements, wouldn’t it be nice to generate a report … Continue reading →

This week, I have had a bit of an epiphany with regard to how we should approach automated testing our projects. Misgivings about TDD style testing The value of TDD style testing comes as an aid to code design rather … Continue reading →