Breakpoint in DLL files ?

[Luk Vloemans]

Hey,

Does anybody know, why Visual Studio has some breakpoints in imported
DLL files? When I try to remove them, the compiler tells me it cannot be
removed, instead she suggests to disable them.

However, the next time I debug, the breakpoints are enabled again..

This causes me to lose a lot of debugging-time, because I must press F5
a lot of times before I get to my coding..

Anybody any Idea ?

Thx,

Luk Vloemans
IT student

[Nicholas Paldino [.NET/C# MVP]]

Luk,

Do you have a small section of code that can duplicate this?

And you are welcome. =)
--
- Nicholas Paldino [.NET/C# MVP]
- ni**************@exisconsulting.com

"Luk Vloemans" <lu**********@student.luc.ac.be> wrote in message
news:et****************@tk2msftngp13.phx.gbl...

Nicholas Paldino [.NET/C# MVP] wrote:

Luk,

Do you mean in the framework classes? Are you sure about this? Can you point out where the breakpoints are? I've never come across that, but if it is in there, then it definitely needs to be removed.

Hey Nicholas,

Well, the breakpoints aren't really in the classes, as I just found
out.. But they're on the "call stack". I don't know how they got there,
and I don't have a clue as to how to remove them.

A small example:

> mscorlib.dll!System.IntPtr.IntPtr(int value = 0)

in the meanwhile, there's something appearing in a "disassembly frame"

> ADDRESS: System.IntPtr.IntPtr
> MESSAGE: Disassembly cannot be displayed.

This is where my visual studio halts.

It's propably a setting from Visual Studio that you can disable, but so
far I've been out of luck..

Any ideas ?

By the way, thx for your help with the threads, I've got a better clue
now :)

grtz,

Luk