So, I ran into an as of yet unsolved problem today. I don’t know if this is a Linq bug, a debugger bug, or a Visual Studio bug, but, for your viewing pleasure:
If I can figure out what’s going on, I’ll post an update
EDIT: Figured it out..
This is one of the big reasons I don’t like operator overloading…
The items inside the FilterList overrode the comparison operators, but did not handle “null” properly…
Grrr..
No comments:
Post a Comment