Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've consolidated answers from several sources. </p> <ul> <li><p>Are you running the debug configuration?<br> In the Solution check: SolnExplorer|Solution|Properties|ConfigurationProperties| Configuration = Debug<br> and: SolnExplorer|Solution|Properties|ConfigurationProperties| Configuration|ProjectConfig[]=Debug -->Note:Although breakpoints will work with release configuration, sometimes the lines may be optimized out or rearranged.</p></li> <li><p>Are you generating debug information? In C# projects: SolnExplorer|Project|Properties|ConfigurationProperties|Linker|Debugging|Generate Debug Info=YES<br> In C++ projects: SolnExplorer|Project|Properties|ConfigurationProperties|C/C++|Debug Information Format = Program Database(/Zi)<br> -->Note: It pays to check the command line arguments.</p></li> <li><p>Is everything is being rebuilt? If the PDB is out of sync, the debugger may not be able to load symbols:<br> In Solution: SolnExplorer|Solution|Properties|Configuration Properties|Build=TRUE(Checked) for all projects.</p></li> <li><p>Can you debug unmanaged code?<br> In C# projects: SolnExplorer|Project|Properties|Debug|Enable unmanaged code debugging = TRUE(Checked)<br> In C/C++ projects: SolnExplorer|Properties|Configuration Properties|Debugging|Debugger Type = Mixed </p></li> <li><p>Are files being put where you think they are? I use a single bin\debug directory for collecting all project DLL's and PDB's.<br> In the C# projects: SolnExplorer|Project|Properties|Build|Output Path = ..\bin\debug<br> In C/C++ projects: SolnExplorer|Project|Properties|ConfigProp|Linker|OutputFile = ..\bin\debug\$(TargetName)$(TargetExt)</p></li> <li><p>Are old files getting in the way? Check the timestamps on all the output files in the bin directory. Make sure they are as of the last rebuild.<br> Some people advise blowing away all the bin and obj directories. This may be worthwhile just to see that old files aren't laying about. Checking the time and date stamps should do just as well. </p></li> <li><p>Has the DLL been loaded? If the Breakpoints are disabled, it may be because the DLL has not been loaded yet. Check Menu|Debug|Windows|Modules.<br> Look for the dlls in the module name.<br> In the same Modules window make sure files are loading from the correct path.<br> If an assembly is shared among several programs, it can be loaded from the GAC.<br> -->Note: You can preload the C/C++ DLL before it is required. Use: IntPtr lpDLL = LoadLibrary(myLibraryName);</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload