Recently I found myself trying to load an old .NET 1.1 application onto a virtual machine that I had just set up. I ran into problems getting the application to load. This was because I had installed MS Server 2003 as the operating system on my virtual machine. Server 2003 comes with IIS 6.0 and is set up for .NET 2.0 applications. 

The .NET 1.1 framework is disabled in IIS 6.0 by default. Because who needs .NET 1.1 anymore, right? Well I did... And you may be surprised at how many legacy .NET 1.1 apps are still out there.

It turns out that it is fairly simple to get .NET 1.1 working with IIS 6. You can enable this either by using the Configure Your Server wizard or you can manually enable it through Add or Remove Programs in the Control Panel. This article deals with manually getting the .NET 1.1 framework working with IIS 6.

If you have been programming for any length of time, you know how important commenting your code is. You comment your code so that you will know how it works if someone, including yourself, has to go back and look at it again later.

One of my pet peeves as a professional developer is that every so often you run across code written by someone else that has not been commented - or is commented very poorly. Non-commented or poorly commented code can be a big hassle for a developer. Suppose you need to fix a bug in someone else's code and this person no longer works with you or your company. If the code is not properly commented then you could spend a lot of time - and time is money - trying to figure out what the code does. Unless you are trying to obfuscate code to make it more difficult for someone to understand, there is really no excuse to not properly comment it. It only takes a few seconds to write a some words about what your code does.