Unless there is a major bug in VS.Net I do not think it is possible. Did you  
  
try to find if that code is ever covered? It is possible that that part of  
  
code is not called and you 'think' should be called.  
  
"Christopher Weaver" <we.aver@nospamverizon.net> wrote in message  
  
news:e7k6QZ1qFHA.2876@TK2MSFTNGP12.phx.gbl...

I'm developing a component housed within a DLL.  Many times I've set  
  
breakpoints within the source code of the DLL and found that they stopped  
  
the execution of the code.  But many times I've set breakpoints in the same  
  
places and they've been ignored.  I'm at a loss as to what might be causing  
  
this.  I've tried rebuilding the solution as well as rebuilding both the app  
  
and component projects separately.  
  
Any ideas on this?

I considered the possibility that my breakpoint was set on a line that was  
  
not being called.  So I placed the breakpoint on the line that contained the  
  
call to the function within the DLL and hit F11.  It behaved just as though  
  
I had hit F10.  
  
"Pohihihi" <pohihihi@hotmail.com> wrote in message  
  
news:%23WWGse1qFHA.2244@tk2msftngp13.phx.gbl...

The can happen when the DLL version does not match the source code. (The  
  
wrong version is deployed, or the system is finding a DLL in a place other  
  
than where you think it is --usually it's in both places...)  It could  
  
happen for other reasons as well.  
  
Also, if your breakpoint icons show as question marks, then I beleive the  
  
DLL isn't loaded yet.  
  
m  
  
"Christopher Weaver" <we.aver@nospamverizon.net> wrote in message  
  
news:%23qlh6%231qFHA.2072@TK2MSFTNGP14.phx.gbl...

Thanks.  
  
"Mike" <vimakefile@yahoo.com> wrote in message  
  
news:ew%23XJM3qFHA.2540@TK2MSFTNGP09.phx.gbl...