By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,713 Members | 1,243 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,713 IT Pros & Developers. It's quick & easy.

BUG: debugger is case-sensitive to paths when resolving assembly refrences

P: n/a
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
Sep 21 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.