I just experienced the infamous “The breakpoint will not currently be hit”. After reading several posts in various websites in reference to this issue, I found few solutions which I thought of sharing :
- Check if the debug=”true” in your aspx page.
Debug is disable
<%@ Page Language=”C#” MasterPageFile=”~/MainMasterPage.master” AutoEventWireup=”true” CodeFile=”Facility.aspx.cs” Inherits=”_Facility” debug=”false”%>
Debug is enable
<%@ Page Language=”C#” MasterPageFile=”~/MainMasterPage.master” AutoEventWireup=”true” CodeFile=”Facility.aspx.cs” Inherits=”_Facility” debug=”true”%>
- Removing all the references in the project and re-inserting them taking care of the version used.
Manually deleting the bin/release and bin/debug sub-directories in every project in the solution.
De-installing and reinstalling .net framework (any version) and VS-2005
Taking a close look at the target platform in the projects.
Breakpoints Should come back !!It can be caused as the .PDB and the assembly of one of the controls would not have been referenced at the right place, resulting in a desync between the sources and binaries.
By re-referencing all, and killing the bin subdirs problem will be solved.
- Goto Tools menu and select Options; check the “Show advanced build configurations” checkbox. Now the build configurations show in the Project Properties dialog; display will be the Project Properties dialog (Project menu/Properties). We can now see the Configuration dropdown box. Select “Active(Debug)” item. Check the “Define DEBUG constant” checkbox. Rebuilt the project. Now there is a symbols file ([project].pdb) in the current output directory. When debugged, the symbols file is loaded and breakpoints will now hit.
- Other options than can be tried are 1). rebuilding the application many times. 2). completely deleting and redoing it from scratch (though thats not a good idea !! ). 3). Check whether the .pdb file is in the same location as the DLL with the same name and time. 4). Check whether project is running on the debug version of the DLL and associated files. 5). ensured there was only one instance of the DLL, project, etc. on the machine. 6). right clicked on a DLL that is within the Modules window, selected Symbol Settings, selected Debugging | Symbols and manually added the directory with the .pdb file – even though confirmed that this is the default location used by the project. 7). checked that Enable Just My Code is not selected within the Symbol Settings | Debugging | General menu. 8). tried placing the DLL in the C:\Windows32\ directory just to see if the Modules Window would “see” it. 9). adjusting a few other things to match suggestions regarding optimization settings, etc. 10). selecting Load DLL exports within within the Symbol Settings | Debugging | Native menu (although I am not familiar with what this may actually be doing..needs some research in the weekend); this caused most of the DLL’s in the Modules window to have a listing of Exports Loaded, but did not appear to affect my issue in any way – again my DLL is not within the Modules window.
- Select the Solution node in your Solution Explorer… Select Properties from the context menu… Select Multiple Startup Projects…For each project you want to debug, select Start from the action drop down.
Received a comment from Eric Long with an other solution: click here .