Friday, May 12, 2006
« New CSLA .NET forum is online | Main | Dynamically loading assemblies from shad... »

I just got back from Norway (so my body has no idea what time it actually is right now...), and one of the conversations I had while there was about data binding a TextBox to an object's property that is a Nullable<T> - like Nullable(Of Integer) or something.

Somehow I had expected that Windows Forms would have anticipated this (obvious) concept and would handle it. Not so...

Fortunately, as a result of this conversation, one of the people at the conference took some of the ideas we were tossing around and came up with an extender control to address the issue. Very nice!


Tuesday, May 16, 2006 4:22:07 AM (Central Standard Time, UTC-06:00)
Hi Rocky, the solution we found workes great. It seems to me that using the Extension Provider model is the correct way to solve the problem. And the beste part, i have also create a DateValidator extension that works perfect i combination with the NullableExtension to validate and parse dates in textboxs.

I think it is a very good approach to use Nullable when binding to WinForms controls. Especially when it comes to validation i think it is a good idea to use Nullable Of DateTime instead of string.

Regard.
Roy
Comments are closed.