Click here to Skip to main content
15,886,067 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
I have never opened a project and today I opened it and was trying to debug, I checked web.config file for both . Both has debug=true in compilation. But Project A doesn't hit debug point and doesn't even show the Debug symbol has pause/play symbol. It just shows green play symbol.
Project B has debugger working and shows all correct.
Can anyone tell me why?
Posted
Comments
Sergey Alexandrovich Kryukov 25-Feb-15 14:08pm    
Sorry, not enough information. There are different methods to screw up debugging... :-)
—SA
sudevsu 25-Feb-15 14:27pm    
What do want me to share to explain it better?
I am not sure of why is this happening to a website but not a windows application. Debugger works for windows application. But not to a website. Both are developed in VS2008.
Sergey Alexandrovich Kryukov 25-Feb-15 15:41pm    
I just don't know. You have to do some preliminary research. How to building the project from scratch using the other files? Something like that.
First, check up all the project Properties. Another possibility is to screw up debugging with code, but with .NET this is extremely rare. I was only one such project, and the problem has gone with VS 2013. So, one possible experiment: open problematic project with VS 2013 and see if it debugs it.
—SA
PIEBALDconsult 25-Feb-15 14:26pm    
It may be due to how the project is referred to in the client project -- either as a DLL (which is unlikely to allow debugging) or as the project itself, which shuold allow debugging.
And the referred DLL may be in the GAC, which causes trouble as well.
sudevsu 25-Feb-15 14:28pm    
I can see solution file and I opened using solution file in VS2008.

1 solution

You may have to attach your debugger to your IIS process to be able to debug your project. For a Windows Application, it is more straightforward, as the process to debug is launched by Visual Studio. For a web site, the code is executed under a IIS process, with the application pool's credentials.

In Visual Studio, click on the 'Debug' menu, then on 'Attach to process...' ; find your IIS process and select it (sorry, I can't recall IIS process name as there are about three years that I did not have to go this way).
 
Share this answer
 
Comments
sudevsu 25-Feb-15 14:41pm    
R u talking about this "WebDev.WebServer.EXE"
I attached this as well. But it didn't help
phil.o 25-Feb-15 14:49pm    
No, I am more talking about a process named iis.exe or something like that :)
WebDev? I thought we were talking about VB/.NET
sudevsu 25-Feb-15 14:51pm    
yeah it is ASP.NET and VB website
sudevsu 25-Feb-15 15:39pm    
Yayyy It worked

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900