I was only thinking the other day, "Wouldn't it be great if someone wrote an add-in to Visual Studio that let you drag tables from a database and it generated NHibernate-compatible class definitions and mapping for me".
Well it appears I wasn't the first to have this idea.
The project seems to be run by Adam Langley. There is some source code available, though not in the SourceForge SVN/CVS repository.
One problem at the moment is that it only generates C# code.
I'd assumed that Visual Studio 2008 would be able to open 2005 projects and manage them alongside any new 2008 projects.
This isn't quite correct - 2008 will upgrade 2005 projects, but those projects can still target the .NET 2.0 runtime. There is a difference!
So if you've got a team project where not everyone is moving to 2008, best keep using 2005 on it.
This morning I thought I'd clean out some of the accumulated dust from my PC at home. I've done this before, as I've noticed that the CPU's heat sink and fan particularly gets quite a covering of dust and lint, and I presume this isn't helpful in keeping things nice and cool.
Things were fine until I tried to lever off the fan that sits on the CPU heat sink. In prying it off, I also managed to unseat the CPU from its socket.
The problem is that the CPU has the heat sink firmly attached to it, and the heat sink is wide enough that you can't access the zero-insertion force lever on the socket.
Initial attempts to separate the CPU from the heat sink were not successful.
I'm confident that the hard disks are fine, though it is a bit tricker than usual as I had utilised the on-board RAID feature of the D865PERL motherboard to stripe two hard disks into one large disk. Because of this I'd prefer to get the CPU back and working rather than have to consider pulling out the hard disks and trying to get them to work in a different PC - even if it was the same model.
Anyway, now that I've got into work, I have found this useful article on removing and re-attaching the heat sink. I'll have another go tonight and see if I can have more success.
It was nice to see that some of the expanded documentation I contributed to the MbUnit site has been noticed by Andrew (the main developer of MbUnit).
That's one great thing about using a Wiki is that anyone (like me) can jump in and add or expand the information.
It also turned out to be a great way to learn about some of the features of MbUnit that I hadn't bee aware of before too.