Concrete Example - Mocking .NET Objects w/NUnit

Geoff Lane does a very good job of explaining .NET Mock objects.

People were requesting a "concrete" example so I implemented an example C# console application (although this can easily be made into an ASP.NET web application).

Geoff hints to using Spring .NET to wire things up, but that might be too confusing for some people. And maybe a little over board for a simple example (open closed principle).

So instead I created a PersonServiceManager that creates a "concrete" PersonService via IPersonRepository injection. The GUI communicates to the PersonServiceManager through an IPersonService interface.

Instead of "mocking" an IPersonRepository, we are actually implementing it then injecting it into PersonService (just like our NUnit test). The PersonServiceManager handles passing the appropriate database connection string down to the data layer. In my example, the data layer object PersonDb (which implements IPersonRepository and used for injection) utilizes the DbProviderFactory.

Here is the sample source (C# Console App).

Also remember that the sample source could be broken down into separate assemblies in a real world project.

Side by Side - IE8, IE6, IE5.5, IE5, IE4.01, & IE3

Running IE8 on your computer? The included developer tools are great. Need to switch to IE7 mode? No problem using IE8.

But what about IE6, IE5.5, IE5, IE4.01, and IE3? Here is a free multiple installer you can use. And it works! And I performed a virus scan (before and after the install)... no problems detected.

Unfortunately, a couple of my JQuery sites look weird with IE6. I know I know, its not JQuery... rather its the IE6 CSS quirks (among other things... standards compliance... cough... cough...).

http://tredosoft.com/Multiple_IE

Visual Studio 2008 Justification

There are two primary justifications for my company's latest purchase of Visual Studio 2008 Professional -

1. The ability to "target" previous .NET versions.
2. The integrated unit testing.

While we still have not setup the automatic builds (command line)... and we still utilize NAnt... the integrated unit testing feature of Visual Studio 2008 rocks. Sure there are alternatives (we still have some projects with NUnit testing)... and various mocking frameworks, however the ability to "right click" create unit test/private accessor is very productive for us.

VB.NET InternalsVisibleTo

Unfortunately, the InternalsVisibleTo attribute does not work with the .NET 2.0 Framework for VB.NET. However, I just installed Visual Web Developer 2008 Express SP1 Beta and it works! Thanks Microsoft for making my NUnit testing a little easier (and cleaner).

To reproduce:

Create a VB.NET class library named ClassLibrary1. Add a single class with only a friend constructor. Add the following attribute to AssemblyInfo.vb:

Assembly: System.Runtime.CompilerServices.InternalsVisibleTo("ClassLibrary2")

Add another VB.NET class library named ClassLibrary2. Add a project reference to ClassLibrary1. Verify that you are able to construct an instance of the above class.