Solved

Missing "ASP.NET" Tab in INETMGR

Posted on 2006-06-13
11
1,394 Views
Last Modified: 2013-11-25
I have a machine with the following installed:

- Win XP SP 2
- Visual Studio .NET 2002
- .NET Framework 1.0, 1.1, and 2.0 (according to Add/Remove Programs)
- ASP.NET 2.0

I only recently installed .NET 2.0 and ASP.NET 2.0.  Now that I've done so, the debugger no longer breaks on break points in my ASP.NET project.  I've seen a couple of notes that suggest running INETMGR, selecting the Virtual Directory properties of my web project, selecting the "New ASP.NET tab" that shows up with installation of .NET Framework 2.0, and checking/changing the debug configuration settings there.  The problem is that this tab does not show up on my machine.  Anybody else seen this problem or know how to address it?
0
Comment
Question by:boothkd
  • 6
  • 5
11 Comments
 
LVL 9

Expert Comment

by:lojk
ID: 16898975
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
0
 
LVL 2

Author Comment

by:boothkd
ID: 16902236
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.
0
 
LVL 2

Author Comment

by:boothkd
ID: 16902340
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.
0
 
LVL 9

Expert Comment

by:lojk
ID: 16902584
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.
0
 
LVL 2

Author Comment

by:boothkd
ID: 16904795
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.
0
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

 
LVL 9

Accepted Solution

by:
lojk earned 500 total points
ID: 16905095
oh, ive just got it!

- Win XP SP 2
>>> Visual Studio .NET 2002 <<<
- .NET Framework 1.0, 1.1, and 2.0 (according to Add/Remove Programs)
- ASP.NET 2.0

I really should have spotted that one sorry   :-o  

You can only develop your applications on the IDE of that .NET Versions which they are assigned to ...

1.0 2002
1.1 2003
2.0 2005

i.e it is backwards compatable only - you cant use .net 2.0 components when using VS2003 but you can use 1.1 and 1.0

There is definitely a link on the microsoft site that basically says do not install .net2.0 on a machine that is running .net1.x applications because it affects all sorts of things including i think the debugger and definitely web applications, cant find the link at the minute but its a known issue. Its what prompted me to Upgrade to vs2005 (the DataGridView Control in .NET2.0 is a massive improvement over the 1.x DataGrid Control and is probably worth the upgrade alone not to mention the SplitContainer and FlowLayout Controls)
0
 
LVL 9

Expert Comment

by:lojk
ID: 16905106
It was your final comment that made the penny drop btw...
0
 
LVL 2

Author Comment

by:boothkd
ID: 16905818
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.
0
 
LVL 9

Expert Comment

by:lojk
ID: 16905851
Cool, consider the upgrade to 2005 it is truly excellent and worth any minor upgrade niggles...

thx for points.

0
 
LVL 2

Author Comment

by:boothkd
ID: 16905865
BTW, I dropped the framework back to 1.0.3705 using aspnet_regiis and the debugger works again.
0
 
LVL 9

Expert Comment

by:lojk
ID: 16905922
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).
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In my previous two articles we discussed Binary Serialization (http://www.experts-exchange.com/A_4362.html) and XML Serialization (http://www.experts-exchange.com/A_4425.html). In this article we will try to know more about SOAP (Simple Object Acces…
Entering time in Microsoft Access can be difficult. An input mask often bothers users more than helping them and won't catch all typing errors. This article shows how to create a textbox for 24-hour time input with full validation politely catching …
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…

896 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now