Hi Steve,
Thank you, the hotfix solved the problem. Actually, I've ran into a new problem after applying the hotfix which I have a workaround for, but thought I would just pass it by you in case any ideas come to mind :-)
In my VS 2005 project settings, I've had the "Start Action" on the "Web" tab set at "Current Page". After applying the hotfix, if the 'current page' is in a sub-directory when I hit F5, I get the following error msg:
"Unable to start debugging on the web server. IIS does not list an application that matches the launched URL."
However, if the 'current page' is in the root of my application, then everything works fine.
In IIS7, I tried making this sub-directory an "application" by right-clicking on the root application name, selected 'Add Application...' and chose the sub-directory. This changes the icon of the sub-directory in IIS7 from a folder icon to an application icon. I can then use F5 in visual studio ... but I immediately get a "could not load type" parser error in my browser essentially saying that the class the page inherits from cannot be found. So, I'm fairly certain this is not the correct way to solve the problem.
My workaround is to simply change the 'Start Action' from 'Current Page' to 'Specific Page', and then not enter a specific page. Since I have directory browsing turned on, I simply get a list in my browser of the available folders / files when starting with F5. This is not really a big deal to just navigate to the folder / page I'm interested in. Although, I would imagine a fix to the "IIS does not list an application that matches the launched URL" error message is probably right under my nose.
Thanks again for your response!
Ben