Bug 20672 - ListChangedEventArgs.PropertyDescriptor is always null in BindingList.ListChanged event args
Summary: ListChangedEventArgs.PropertyDescriptor is always null in BindingList.ListCha...
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: 3.4.0
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-06-18 05:20 UTC by Prashant Cholachagudda
Modified: 2014-08-07 02:21 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Prashant Cholachagudda 2014-06-18 05:20:29 UTC
It seems like a bug on the PropertyDescriptor value in the ListChangedEventArgs when using a BindingList.
ListChangedEventArgs.PropertyDescriptor is always null in BindingList.ListChanged event args

Here's the unit tests that pass on .Net 4.5 profiles but fails on Mono
https://gist.github.com/prashantvc/88f6072dc753697c9738
Comment 2 Alexis Christoforides 2014-06-18 22:24:19 UTC
Hello,

This has been fixed in master (commit aeab5b59021f4a712d54357c8bbeaa6fac12dc37). 

I'll also commit an amended version of your unit test if that's okay, Prashant.
Comment 3 Stefan de Vogelaere 2014-06-19 14:11:26 UTC
Hi,
When can we have this fix in Monotouch? It's urgent..,
Comment 6 Saurabh 2014-08-06 10:12:27 UTC
Could you provide me Test project so that I can check this issue at my end?
Comment 7 PJ 2014-08-06 10:21:01 UTC
Alexis, where were the tests added after comment 2? We might be running them on Android already on wrench.

Saurabh is seeing this bug listed in the Android 4.16.0 release notes so he's trying to verify the fix for Android.

Saurabh, you can add the tests in comment 0 to an Android unit test project and run them yourself to verify.
Comment 8 Saurabh 2014-08-06 11:33:34 UTC
I have check this issue with code mentioned in comment 0 in Android Unit Test Project. I am successfully able to Run test on device with X.Android 4.16.0-3 and Mono 3.8.0. I have also tried to reproduce this with X.Android 4.14.0 and Mono 3.6.0, Here also I am successfully able to Run Test on device. I am not sure what changes happened?
Comment 9 Alexis Christoforides 2014-08-07 02:21:07 UTC
Hey,

The test is in mono/master commit 5bdff7c7e99511d42445bd15d570789100c263af.  The test fixture can be quickly run with "make check FIXTURE=System.ComponentModel.BindingListTest" within mcs/class/System.