Comments
Sort by recent activity
Brilliant! I swear you guys are reading my mind! [image] / comments
Brilliant! I swear you guys are reading my mind!
Thanks for the info.
I've now discovered the cause of my confusing results, in case it helps anyone. Localization._attributesOnObjects is the storage used when the Localization.Attributes attached property is set on an object that isn't a DependencyObject. In our case we were setting it on some DataTemplates and HeirarchicalDataTemplates to stop our L18n tool's automatic simulated translation messing them up. That turns out to have been a bad idea. System.ComponentModel.ReflectPropertyDescriptor turned out to be a signpost to a genuine WPF memory leak, as described here: http://support.microsoft.com/kb/938416
In our case we're doing View-PresentationModel (similar/same as MVVM) and some of our PMs weren't implementing INotifyPropertyChanged. As the View & the PM reference each other, that was triggering the leak. Implementing INotifyPropertyChanged or setting the Mode of the view's bindings to the PM to OneTime fixes the leak.
Many, many thanks again for v5. I can't imagine how I would have tracked all this down without it.
Is there any way of extending the trial of the RC? Mine's about to run out, but we've got 10 full ANTS ".Net Bundle" licences (with 1 year's worth of free upgrades) that we bought in Dec/Jan. / comments
Thanks for the info.
I've now discovered the cause of my confusing results, in case it helps anyone.Localization._attributesOnObjects is the storage used when the Localization.Attributes attached p...
Actually, I just looked, and the necessary Source Server functionality should be in DbgHelp.dll as SymGetSourceFile. See MSDN. / comments
Actually, I just looked, and the necessary Source Server functionality should be in DbgHelp.dll as SymGetSourceFile. See MSDN.
Cheers, Stephen.
Alain-Daniel: Sorry for hijacking your thread. It looks like your issue is more complex than mine! / comments
Cheers, Stephen.
Alain-Daniel: Sorry for hijacking your thread. It looks like your issue is more complex than mine!
My problem seems to have been running unit tests through the MbUnit GUI. (I was doing a quick demo of ANTS to a colleague.) Running the same tests through the MbUnit console works fine. Maybe it's something to do with the MbUnit GUI running the tests in a different AppDomain?
This is using Vista or XP, .Net 3.5 SP1, VS2008 SP1 (not used during test) & MbUnit 2.41.232.0. / comments
My problem seems to have been running unit tests through the MbUnit GUI. (I was doing a quick demo of ANTS to a colleague.) Running the same tests through the MbUnit console works fine. Maybe it's ...
I'm having the same problem yesterday (on an eval license). I'm just getting the timings for the whole method displayed next to the first (executable) line in the source.
Any hints for debugging the issue? / comments
I'm having the same problem yesterday (on an eval license). I'm just getting the timings for the whole method displayed next to the first (executable) line in the source.
Any hints for debugging th...