[Mono-winforms-list] Private ImageList methods removed in r69012

Chris Toshok toshok at ximian.com
Wed Dec 6 09:24:37 EST 2006

do we know that the designer in visual studio behaves as if it can call
these methods?  The designers of course have to use reflection to find
the methods, but in the other cases these methods aren't private.  If
visual studio behaves as if the methods are there, we have another piece
(besides the msdn docs and corcompare output) we need to look at to see
which methods needs implementing.


On Wed, 2006-12-06 at 14:37 +0100, Kornél Pál wrote:
> Hi,
> The removed methods were private but they were intended to be used by 
> designers.
> This feauture is documented:
> http://msdn2.microsoft.com/en-us/library/53b8022e.aspx
> Also note that I noticed the behavior in Visual Studio designer that can 
> only be implemented using these methods.
> And I belive that it is legal to call these methods using reflection and 
> study their behavior altough it wasn't necessary.
> Applications should not rely on the presence or absence of these methods if 
> they are private but a properly implemented designer (or maybe other 
> applications) can call these methods and the absence of these methods will 
> result in different designer behavior regarding the default property values.
> Kornél 
> _______________________________________________
> Mono-winforms-list maillist  -  Mono-winforms-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list

More information about the Mono-winforms-list mailing list