This documentation is archived and is not being maintained.

Debugging Changes in Visual Basic .NET

Although the process of debugging an application in Visual Basic .NET is essentially the same as it was in Visual Basic 6.0, there are a few differences you will want to be aware of. In addition, there are several new features related to debugging in Visual Basic .NET. For more information, see What's New in the Visual Studio Debugger.

In Visual Basic 6.0, in most cases you could make changes to your code while in break mode and continue debugging without stopping and restarting. In Visual Basic .NET, any code changes in break mode require that the project be rebuilt before the code changes can take effect; edit and continue is no longer supported. For more information, see Limitations of Edit and Continue.

In Visual Basic 6.0, syntax errors in code would cause an error message dialog box to be displayed during debugging. In Visual Basic .NET, most syntax errors appear in the Task List window at design-time; run-time exceptions appear in the Output window. For more information, see Debugging Basics.

Some of the keyboard shortcuts for debugging are different in Visual Basic .NET. For example, in Visual Basic 6.0 the F8 command was used to step into code; in Visual Studio .NET the F11 command performs the same function. For more information, see Integrated Development Environment Changes in Visual Basic .NET.

In Visual Basic 6.0, expressions could be evaluated and values could be set in the Immediate window. In Visual Basic .NET, the Command window replaces the Immediate window; when in Immediate mode, the functionality is the same. Visual Basic .NET also supports several new options for expressions. For more information, see Expressions in Visual Basic.

See Also

Debugging | Debugging Managed Code | Introduction to Visual Basic .NET for Visual Basic Veterans