Fun VS2005 bug, bad case handling
I found a fun VS 2005 bug today:
- Run an application with an
assertthat’s hit - Bring up the JIT debugger, based on Windows/Studio prompts
- Edit and save a file while (or after) debugging from that VS session
- If the file’s name was mixed case, Studio will save it in all-lowercase (and now you have 2 files with similar names)
- The new file will also have its line endings munged/reversed/mixed
I’ve seen this bug before, but have never been able to reproduce it reliably. Reverting it, of course, requires moving the changes to the original file by hand (or the diffs will be messed up).

RSS