Compatibility Issues From IIS 5.0 To IIS 6.0

Our company has an application (CB/VSV) working on Win2K/IIS 5.0. Recently I was assigned the task for investigating CB/VSV compatibility issues on Win2K3/IIS 6.0. Here is a couple of issues I found:

• The default installation of IIS on a Windows 2003 Server doesn’t include the support of ASP.NET. If you apps are .NET application, you must check the ASP.NET option. Both the ASP.NET subcomponent and the IIS subcomponent are components of the Application Server component. After installing the ASP.NET component, one Web Service Extension named “ASP.NET v1.1.4322” is added to the list of Web Services Extensions and is allowed by default.
• All the Web Service Extensions are prohibited by default. The URL of the login page of our app is "http://localhost/portal/bin/home.dll". So IIS 6.0 doesn’t know which executable maps to home.dll by default. I have to Allow the “All Unknown ISAPI Extensions” extension in IIS 6.0.

MSDN provides samples on Using System.DirectoryServices to Configure IIS. I couldn't find documentation at MSDN about the names of the properties of a DirectoryEntry object representing a virtual directory. The way that I approach this is to enumerate the properties of a virtual directory. Save the data in a file and then I change the properties that I’m interested in manually. Then save it again in another file. Finally I compare the two files using WinDiff to figure out the names of the properties that I’m interested in.