This documentation is archived and is not being maintained.

Breakpoint Failure

This topic applies to:


Visual Basic




Web Developer


Topic appliesTopic appliesTopic appliesTopic appliesTopic applies

Pro, Premium, and Ultimate

Topic applies

Topic applies

Topic applies

Topic appliesTopic applies

If two or more source files in the project have the same name, the debugger might have trouble determining which file the breakpoint is set in. This often occurs if you create a module with the same name as a component of the Debug library you are linking to.

To fix this problem, enter the full path for the source file. You can change the file path name in the File Breakpoint dialog box. For more information, see How to: Edit a Breakpoint Location.

In other cases, the debugger might not locate the source file that corresponds to a breakpoint, even though the source file exists. This occurs if a source file has changed and the source no longer matches the code you are debugging. If you want Visual Studio to display source code that does not match the version you are debugging, clear the Only use source code that exactly matches the original version option in the Debugging node of the General category in the Options dialog box. You can also bind the breakpoint by checking Allow the source code to be different from the original version in the File Breakpoint dialog box.

Other Resources