During a .NET 4.0 -> .NET 4.5 application migration process I\'ve discovered an extremely strange behavior. I\'ve been able to track this issue down to this short code snipp
According to Microsoft, this is by-design.
See here for full details:
Despite MS saying it's "by design", I still think it's a bug!