Just tried the new v3.0. But unfortunately, the bug is getting worse.
As I want to re-explain my example above:
- interface definition = IEntity
- interface definition = IAccountEntity : IEntity
- class definition = Entity : IEntity
- class definition = AccountEntity : Entity, IAccountEntity, IEntity
I have a data source in a form of collection of AccountEntity, but cast-down in the form ICollection<IEntity>.
Now that using v3.0, there are two obvious results obtained
1. The type of the collection (from the VS Visual Debugger) is IEntity, instead of AccountEntity.
My poing is that although ICollection<AccountEntity> has been casted down to ICollection<IEntity>, the object in it is actually still an AccountEntity, not an IEntity.
2. Using AutoCreateColumns set to true, it turns out that only properties from IEntity are shown. Other properties from AccountEntity, IAccountEntity, and Entity are completely missing.
So, is there any good explanation for this? Am I missing something here?
Thanks!
P.S.:
- one good thing I observed, the data grid assembly doesn't refer to System.Windows.Forms.dll assembly anymore. +1
- still no further explanation about ReadOnly property name, which should be, IMO, IsReadOnly (BTW, I just notice that DepedencyProperty also use "ReadOnly" for one of its property name, hmm...)
Regards,
Maximilian Haru Raditya