[Mono-bugs] [Bug 417973] DataBinding: support multi-level dataMember strings

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Sep 8 10:07:10 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=417973

User andyhume32 at yahoo.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=417973#c3


Andy Hume <andyhume32 at yahoo.co.uk> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                                        |NEEDINFO
      Info Provider|                                                |andyhume32 at yahoo.co.uk




--- Comment #3 from Andy Hume <andyhume32 at yahoo.co.uk>  2008-09-08 08:07:10 MDT ---
Cool I'll have a play.

I have a list of planned tests.  I'm banging away at 2.0 and other things just
now, so you might get to these before me.

1. Multi-stage properties path -- this one.

2. Same as 1. but with a property exposed only by ICustomTypeDescriptor.
Tests patch nearly ready.

3. Everything required for DataSet usage and testing.  IIUC it uses
IListSource, ICustomTypeDescriptor, etc.
I guess we can't refer to DataSet in SWF unit-tests so ideally we'll create a
fake equivalent...

3b. One current issue with DataSet is that "foreach (object x in
((IListSource)ds).GetList()) ..." is NIEX.

4. Test the conversion/formatting/parsing processes.  The sample from the
Binding class help in MSDN exposes that we only look fot the TypeConverter on
one of the types and not on both source and target.
There's a page and a half in Noyes' DataBinding book listing the various
conversion actions -- I *think* we do most. :-)

5. Is it possible for one of the first segments in a multi-stage path to be a
list type?  If so we need to test that.

If you're looking at the MSDN sample(s), then that will probably expose
everything.


I don't have commit privileges BTW...


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list