In my last post, I wrote about a memory leak that is easy to come by in WPF. I converted the WPF test application I was using to Silverlight to see whether or not Silverlight suffers from the same memory leak.
Turns out it doesn’t! Classes get disposed just as you would expect them to. It’s nice that at least one of these platforms doesn’t have this bug, but I think it’s too bad that we can’t expect consistency between WPF and Silverlight.