Not doing what you want

I'm writing:
Validation.AssertIsTrue(
Directory.Exists(pathToLogDirectory),
"Supplied path does not point to an existing directory");

I'd like to write something like:
Assert.That(
Directory.Exists(pathToLogDirectory),
Returnes.True,
Otherwise.Throw(
new ApplicationException("Supplied path does not point to an existing directory")));


One day when the grass is green, the birds are singing and this god forsaken mainframe provides with me with flawless response buffers I'll nuke the Validation class and write, or steal depending on if it's already been done, the Assert.That concept.

Afaik it's only the Nmock2 team that has anything that expressive in the works, but as usual I could be dead wrong. If so, please tell me.

Hunter S. Thompson Q&A Session

As I'm currently reading Fear And Loathing On The Campaing Trail '72 my colleague Mark Rowlands was kind enough to provide me with a recording from a Q&A session at the Boulder University, Colorado that he did in '77. Great fun. I'll put it in my iPod first thing when I get home.

.Net COM-interop DLL registration

I've been working on a project that has sort of a thin service layer that's exposed to some legacy COM-clients. When developing on my local machine I let VS.Net take care of the registration. For stage and production I produced, what I thought was, a really simple solution with a .bat script that simply runs RegAsm. I had to play around with the arguments untill I found out that /codebase was the switch that worked best. This worked very well on one machine and not at all on another etc etc.

After a terrible attempt to put the code in production yesterday I got frustrated enough to throw the .bat file approach out the window and produced a MSI installer for the solution. No more problems. No more .bat script. No more registration problems. Next, next, finish. Love. Peace. Harmony.

And then the frustrated question, why didn't I do that in the first place?