Removed the samples

These have become a bit tedious to keep up to date and I want to have a
clean Framework only repository.
Upgraded NServiceBus to 4.4.2
Upgraded Castle Windsor 3.2.1
Upgraded Castle Windsor 3.2.1 cont..
Fixed some tests
Upgraded log4net
added nicer error if aggregate root isn't found

The previous error was not clear on the actual issue. This has helped
our usage.
Part of the NSB upgrade need to specify msg types

In NSB 4 ICommand and IEvent were added to the NServiceBus namespace.
Clasing with the NCQRS interfaces of the same name.
More NSB  namespace clasing
NSB EventMessage Changes

Ok so with NSB 4 you can no longer have generic type messages. This
meant the original implementation of EventMessage<T> was not valid.

For our companies implementation we had a single NSB Message Handler for
EventMessage and then put the Event payload onto an InProcessEventBus
where the actual NCQRS IEventHandlers took care of the event handling.
This simplified the NSB configuration as we only have to register one
type (EventMessage) as a NSB event.
Adding RegisterInterceptor to the NSB config.
Batching Commands

Ok this change has a bit of code smell in our project, however it is
absolutely giving the desired results even tho we believe it's getting
there incorrectly.

Our domain has lots of small aggregates and some of our user workflows
involve the creation of many of these aggregates at once in various
combinations.

We ended up having a 'batch' of create commands that we wanted to submit
as a single transaction. I.e. if any of the commands failed for whatever
reason the entire batch of commands failed.

We do this by having creating a CommandMessage with a payload of
ICommands. When our NSB-Application Service processes this single
message it just loops through the commands for execution.

In our environment this is working and giving the desired results...
however we THINK this is happening not because of some elegant UoW
transaction handling in NCQRS (because that only exists on a per command
basis) but instead on an NSB - SQL SERVER - DTC magic.

For now we're happy with this results but will investigate a 'better
way' to achieve this functionality within the framework.
apparently this went up