If you are stuck using MSTest as your unit testing framework you may run into problems if any of your tests depend on external files.

MSTest creates a TestResults directory:

A directory made up of your login name, computer name and a timestamp:

and a In and an Out directory:

 MSTest then copies all referenced assemblies to the Out directory and runs the tests in that directory. The problem is that MSTest does not recognize any XML configuration files (besides App.config) as dependencies and they are not copied to the Out directory so your test fails.

To remedy this you need to specify your external dependency as a deployment item in an attribute at the beginning of your test and specify the path to the deployment item:

[TestMethod]

[DeploymentItem("WindsorTestConfiguration.xml")]

public void ShouldUseDependencies()

{

    IWindsorContainer container = new WindsorContainer(new XmlInterpreter(@"WindsorTestConfiguration.xml"));

    Assert.IsNotNull(container);

}

At work I was given the opportunity to build a new piece of complex functionality for the application that I have been working on for the last 6 months. After taking the excellent Nothin But .NET training course instructed by Jean-Paul Boodhoo I decided to try building the new functionality using the domain driven design techniques I learnt at the course.

To me, the domain driven design section of the course was a real eye opener, it taught me to concentrate on the problem I was trying to solve and not worry about infrastructure code. 

To start off the process I met with the domain expert and tried my best to come up with a ubiquitous language that made sense to both of us. It was hard not to talk about interfaces and classes with the domain expert. I even noticed that the domain expert at times would try to translate things into technological terms for me.

Next I created a new solution completely separate from the solution that already existed. My reason for doing this was that before I even started trying to create the new functionality for our system, there was data waiting for me in the database whose sole purpose was to assist me in solving the problem at hand. That data to me, would only distract me from solving the problem and have me worrying about how I was going to get it out of the database.

I wrote my tests first and refined the design of the domain a little at a time only when a new problem presented itself. The next thing I new the problem I was trying to solve had solved itself slowly using tests and small concentrated refactorings. The hardest part was not getting ahead of myself and trying to stay disciplined throughout the process.

I am pretty proud of the solution I eventually came up with although I know that there is room for improvement in the steps I took to solve the problem and the code that I eventually came up with. If you have done domain driven design at work and have any tips for me I would love to hear them. This experience was highly rewarding and I'm not sure if I can go back to the way I coded before.

After learning about the MbUnit plugin for ReSharper from JP at the Nothin But .NET bootcamp, I was really happy to see that James Kovacs has come up with a VsTsUnit plugin for Resharper. If you are forced by your client to use the MSTest for your testing this is something you should install to make your life easier.

This is very cool, on March 14th the Edmonton Agile Methods User Group will be holding its first meeting.  The group is language agnostic so as long as you are interested in learning about Agile methods you are welcome to attend. If you are interested in attending, please RSVP on this thread to give the organizers a better idea of how many people will be attending.

Here are the details:

EAMUG FIrst Meeting!
=================

First off, I would like to thank Rod for obtaining a room for us to hold EAMUG's first meeting! I will do an introductory presentation about agile methods that will last about an hour and a half. I expect we'll probably have another half hour of discussion afterward. I will try to cover the following topics during the presentation:

• Why agile methods? Here I will talk briefly about the origins of  agile methods and the problems they are meant to resolve. 
• Scrum - I will outline the basic techniques of the Scrum project management methodology. 
• XP - I will outline the basic values and practices of XP. Many agile projects combine Scrum as a generic project management methodology with XP for the aspects of the project that are specific to software development. 
• Finally I will discuss some caveats - dangers and pitfalls faced by agile projects. Also I may bring up some of the impediments to adoption of agile practices and how those may be overcome.

LOCATION AND DATE:
=================
115 in IBM's Innovation Centre (10044 108 St. main floor) for Wednesday March 14 at 6PM onwards.  It holds maximum 54 people and comes with a projector to use.To get into the centre, just enter through the main doors of the building on 108 St. just behind the IBM sign (the building is actually  called 44 Capital Boulevard).  The centre is located behind the big glass doors. We will make sure the building and centre doors are open between 5:50 and 6:10.  If you arrive after 6:10 and the doors are locked, please ask the security desk if he can let you into the Innovation Centre to attend the EAMUG meeting in room 115.  I'll make sure the security desk has the heads up for you.

Below is the text of an actual email I received from Microsoft events notifying me of the Unify 2007 Tour. The correct information can be found here if you are interested in attending.

The  Unify 2007 Tour is almost here

You registered for the Unify 2007 Tour in <city name>. This is just a reminder to let you know it’s happening just 10 days from now, on <Month 00, 2007>.

Please bring the Admission Ticket you received at the time of registration to present at the door to gain admittance to the event.
Although the event doesn’t start until 9 A.M., registration starts at 8 A.M.

We recommend you arrive early to get breakfast and to ensure a seat, as those individuals on our wait list will be allowed admittance five minutes before the event begins. Once again, thank you for your interest in the Unify 2007 Tour. We look forward to seeing you there!

Your confirmation details:
Name:  <CONTACT FULL NAME>
Confirmation Number: <CONFIRMATION NUMBER>
Event Code: <EVENT ID>
Event name: <EVENT NAME>
Location:
Room: <VENUE SITE ROOM>
City: <VENUE CITY>
Event date: <EVENT START DATE>
Start time: <EVENT START TIME>
End time: <EVENT END TIME>