P
PJ6
DotNet has always had quirky problems with debugging DLL's when running
inside of other projects - sometimes, mysteriously, you get unhittable
breakpoints (question marks), or break points that get a "plus" sign next to
them and gain "children". Sometimes it's your own fault and the cause is
obvious, but on occasion these things happen for no apparent reason... now
I've uncovered an unexpected cause.
Reference comparisons are case-sensitive: if one project references an
assembly with the path C:\foo\something.dll, and another references the very
same assembly with C:\Foo\something.dll, the VS.Net debugger can decide to
treat these two references as *different* assemblies.
I would call this a bug.
Paul
inside of other projects - sometimes, mysteriously, you get unhittable
breakpoints (question marks), or break points that get a "plus" sign next to
them and gain "children". Sometimes it's your own fault and the cause is
obvious, but on occasion these things happen for no apparent reason... now
I've uncovered an unexpected cause.
Reference comparisons are case-sensitive: if one project references an
assembly with the path C:\foo\something.dll, and another references the very
same assembly with C:\Foo\something.dll, the VS.Net debugger can decide to
treat these two references as *different* assemblies.
I would call this a bug.
Paul