Ever since the .NET Framework introduced generic types (specifically by way of reification) I have named any file containing a generic type in the following form: MyGenericTypeName`n.ext where n = the number of generic type parameters.
This way, I could have multiple types with the same name, differing only in the number of generic type parameters (zero to n) without stuffing them all in the same code file. This has work flawlessly until...
Recently, I have noticed strange behavior when debugging some types. It seemed to happen specifically to generic types but I could not pinpoint a cause. I would either be able to step through the debugger and get odd hexadecimal values (memory addresses ?) with the language indicator set to C++ even though I was using C#. Other times, a breakpoint would indicate "The breakpoint will not currently be hit. No executable code is associated with this line. Possible causes include: conditional compilation or compiler optimizations", and I could not step through the code.
As it seems, there are two bugs reporting these behaviors:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=321714
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=308487
I hope this will eventually be fixed.
0 comments:
Post a Comment