Visual Studio Development Bookmark and Share   
 index > Visual Studio Debugger > Debugger not breaking at error
 

Debugger not breaking at error

New computer, new installation of VS.NET 2005.

Working with an ASP.NET application that came from the previous computer. There is a bug in the application. However, instead of stopping execution at the point in the code where the bug exists, I am being shown the usual ASP.NET error page.

Other info:
I open the application with VS.NET using File->Open->Web site.
The application is installed under IIS
The configuration being built is the debug configuration
I tried killing the aspnet process then deleting everything out of C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\myAppName and the solution file
This problem does not occur for all errors: I changed a parameter name in a SQL Add Parameter and the error was caught. The error that is not being caught is a System.Web.HttpException: Multiple controls with the same ID 'id632871324000000000' were found. FindControl requires that controls have unique IDs.

This behavior is new to this computer ( I think).

I look forward to hearing your suggestions for resolving this problem.

GRoston  Sunday, July 02, 2006 2:57 PM

Hi

I get the same problem as you mentioned. Have you got answer for if yet? if so, pl. share

Padma

PadmaSoumiyan  Friday, August 11, 2006 9:38 AM

Padma,

I think that we resolved the underlying problem, but never did figure out this odd behavior. (The problem was that we were not providing an ID for dynamically generated controls.)

GRoston  Saturday, August 12, 2006 9:14 PM

You can use google to search for other answers

Custom Search

More Threads

• Detecting debugger thread is access property getter / setter.
• The infamous "No symbols have been loaded for this document"
• visual studio 2003 fonts
• Unable to debug: The binding handle is invalid
• just-in-time (JIT) debugging instead of this dialog box.
• Cannot connect to Debugger on web server
• Error connecting to SQL server 2000, unable to debug in VS.NET 2003. HELP?!
• SystemOutOfMemory
• Remote debugging
• Index out of bounds??