Article ID: 325118 - View products that this article applies to.
This article was previously published under Q325118
This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Visual Studio 2005 or in Microsoft Visual Studio .NET, when you click Step Into on the Debug menu or when you press F11 to start your Microsoft Windows-based application, the debugger does not step into any startup events in the form after the constructor is called. For example, the debugger does not step into the Form Load event.
This problem occurs because the code that is generated between the constructor and the Load event of the form does not have debugger symbols. When the debugger contacts the code that does not have the debugging symbols, it does not step.
To work around this issue, set a breakpoint in the event that you want to step through.
Steps to reproduce the issue
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/317297/ )Roadmap for Debugging Hangs, Memory Leaks, Deadlocks, and Race Conditions in Visual Basic .NET
Article ID: 325118 - Last Review: February 27, 2014 - Revision: 5.9