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.
This behavior is by design.
Steps to reproduce the issue
In Visual Studio 2005 or in Visual Studio .NET, create a new Windows Application project by using one of the following:
Microsoft Visual Basic 2005
Microsoft Visual Basic .NET
Microsoft Visual C# 2005
Microsoft Visual C# .NET
Microsoft Visual J# 2005
Microsoft Visual J# .NET
By default, Form1 is created.
In the designer view, double-click Form1 to open the Form Load event in the code view.