…standing on the shoulders of giants…
Unit testing is a tricky beast. As with all unit tests it is important to abstract any dependencies – so in the case of EF it’s the data persistence source. This must be handled carefully because EF creates a container that performs the interaction with the data source. Abstracting that container (via mocking or stubbing)... Continue Reading →
As a .NET developer I don’t like using third party controls when there is tooling available from MS that will do the job I need. For example I prefer using the “baked in” MSTest suit as opposed to NUnit or MBUnit. The same is true for a mocking framework. I have tried with varying levels... Continue Reading →
How many chances do you give a new piece of software before moving away? That probably depends on the type of "chances" you are giving. If you are irritated by a new UI, then you can probably live with it? If the application crashes and you lose all your work, then you'll be less forgiving.... Continue Reading →
Mark Cooper 