Missing "ASP.NET" Tab in INETMGR

perhaps you should check out this link...

How to repair IIS mapping after you remove and reinstall IIS
http://support.microsoft.com/default.aspx?scid=kb;en-us;306005

Also you need to make sure you are a debugger user and ive got a funny feeling there is a reference somewhere on the knowledgebase saying that your ASP.NET user (and/or whatever account runs the IIS) needs to be added to the debugger users group too...

See if the

"%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe" -i

sorts it out first though...

hth

Yeah, I checked that link out and a few others.  I have run aspnet_regiis install from the V2 folder and when I run INETMGR and look at the Properties of the Web Sites folder it shows "ASP.NET_2.0.50727.42" and the path to the executable is V2 folder.  I went ahead and rebooted just to make sure that the install truly was finished with everything, and the code runs, but it won't break at the break points and the ASP.NET tab still doesn't show up in INETMGR (and yes, the project is built for debug ;) ).  I also double-checked the "Debugger Users" group and both I and the anonymous user are in that group.

The article you cited refers to another article, http://support.microsoft.com/kb/325093/ .  That article also suggests re-registering aspnet_isapi.dll (found in the same folder) using regsvr32.  When I tried that, however, Windows threw an error message stating that there were no entry points for aspnet_isapi.dll.  That usually tells me that the dll is not an installable component with an interface but that it is simply a linkable dll.

I've read some other notes that make me wonder if this configuration is even supported; they give me the impression that a V1 framework app might not run properly in a V2 framework environment.

Thanks for the thoughts; I'll keep digging.

One other thing I didn't mention is that the output window in VS  displays the line "Auto-attach to process '[4308] aspnet_wp.exe' on machine 'computer name' succeeded." when I start the app, so I think the debugger is connecting successfully to the IIS process.

sounds like your app is referencing the release version of a an icluded project dll rather than the debug one even if your app is in debug...

if cipying all source to another similar environment on another machine doesn't fix the problem I think I'd rebuild the solution from its components agin..

good luck.

Well I tried all of the above, even deleted the Debug folder contents as well as other VSWebCache stuff and rebuilt, all to no avail.  I finally uninistalled .NET 2.0 framework and reinstalled .NET 1.0.3705 and the debugger is working again.  Note that I tried 1.1.4322 and it did not work then either.  Thanks to both for the help.

It was your final comment that made the penny drop btw...

That's what I was looking for.  I had read some comments that implied this but didn't say it explicitly so I wasn't sure (I'm sure it is written explicitly somewhere in the haystack).  The problem I have with upgrading is that the server for which I'm developing is still running older framework apps.  I've used vs2005 a little and like some of the data control changes also, but I'm kind of locked in on this particular machine.

Thanks for the info.

Cool, consider the upgrade to 2005 it is truly excellent and worth any minor upgrade niggles...

thx for points.

BTW, I dropped the framework back to 1.0.3705 using aspnet_regiis and the debugger works again.

Excellent - Im quite lucky i suppose because my current employer has no existing legacy apps that i have to put up with so i can write everything in 2.0...

Glad to be of help (and youve reminded me to be concious of this scenario for the future).