When I started blogging I wrote my own blogging engine as a way to improve my ASP.NET skills. It was a nice project, but as other blogging engines became more advanced I didn't have time to keep up. So I've wanted to move my blog to another engine for a while. There really is no point in reinventing the wheel and I have more exciting projects now.

I heard about Oxite while I was looking into ASP.NET MVC. MVC is way of structuring applications and has been around for ages, but ASP.NET MVC is a new thing and a thing that I'm quite excited about. Oxite started life as an MVC example and isn't a polished product yet. However, I thought it would be an excellent way to become more familiar with .NET MVC.

It didn't quite meet my needs out of the box. In particular I didn't want my old URLs to break. So I've hacked it about a bit and in the process learnt a lot about MVC. I'm slightly dreading the planned update to Oxite though as the modifications I've made will probably get in the way, but I'm sure the updates will be worth it. I was surprised and pleased when one of the Oxite developers got in touch via twitter to check if I liked Oxite and to offer any help if I needed it. I did end up needing it and he was very helpful, so big thanks go to Erik Porter.

I'm due to start my first .NET MVC project in two weeks and playing about with Oxite has been a big help.

I created this simple app recently to print out all the tables in an SQL Server database. It shows each table's name, description and information about all its columns. I mainly use it when I start on a new project that has an existing database that I need to fully understand.

This is an ASP.NET app, but it's based on the code from Jim Rutherford's ASP SQL Server Schema Printer.

It's just an ASP.NET page. First you need to add your database connection string and then you upload it to your webserver.

You can download it from here:

• Simple SQL Server Database Schema Printer (ASP.NET)

The weather in Leeds lately has been very random. Sunny one minute, torrential rain and thunder the next.

To help others know what weather I'm experiencing, I've made a handy ASP.NET control that displays the weather in Leeds. It shows a picture of me experiencing that weather and can also tell you the weather in several other places I've been to.

It can also change how the whole site looks based on the weather, but it doesn't do this at the moment. You can see this control on the right hand side of my blog's homepage.

In my drive to sort out my development processes there are a few things I want to do. Top of my list is proper automated testing and creating automatic documentation.

Doing these steps every time I compile my site (or application) will add a lot more steps, so I thought it would be better to learn how to automate the build process first.

I'd heard that NAnt was the tool I should be using, but I found it a little bit overwhelming.

NAnt is a program that follows a list of instructions in an XML file called a build file. These instructions are used to do a series of tasks like the following:

• Compile a site's ASP.NET code behind files
• Compile some unit tests
• Copy some files
• Run the unit tests
• Run a program to create documents

It took me a while to get my head round it, but I finally got a simple build file working. I found Jean-Paul Boodhoo's NAnt starter series very helpful.

Next I'm going to get the testing working and then automate it using NAnt.