I'm not a programmer (a fact that for some reason sometimes surprises people when I tell then), and I used to be a hands-on IT guy, configuring and setting up complex systems and troubleshooting. All that respectable, "real" work is - for the most part - in the past. Now I supervise teams that do all that legitimate work.

But now and then I have to do things myself. In setting up a dedicated server for this blog, I found I needed to run applications with multiple versions of the .NET framework - in my case v1.1 and v2 both. I know how to assign the versions of .NET to the applications, but what I did not realize (because I had never had to worry about it on a single server myself) was that there's a bit more to the game than just assigning a framework version to your app and web server instance.

Luckily for me, Scott Forsyth covers just this on his blog in a post entitled "Running Multiple Versions of the Framework in .NET," which I found most useful. Thanks to Scott for the easy to follow post. Apparently it's a IIS v6 thing. I don't remember this behavior in IIS v5.