I’m happy to announce the public release of Excentrics World Server Controls v2.0, RC2! While there haven’t been many changes since the RC1 release, there was a notable change that I believe a lot of users would benefit from if the control set was released. If you’re new to the next version or Release Candidates, please read my RC1 release post.
If you’re interested in test-driving, I’m waiting for you! Help continue flushing out bugs in Server Controls v2.0 prior to it going RTM.
Enjoy this new Release Candidate community!
This has got to be one of the funniest songs I’ve heard of in awhile. The odd thing is that it speaks to me as well, has a catchy tune, and only costs $1 to buy it from the guy! Without further ado..."Code Monkey" by Jonathan Coulton.
“Code Monkey like Fritos
Code Monkey like Tab and Mountain Dew
Code Monkey very simple man
With big warm fuzzy secret heart:
Code Monkey like you”
Looking for Excentrics World Server Controls v2.0, RC1? I thought so. Check it out!
So ever since I introduced the concept of “nullability” for the CalendarPopup and TimePicker controls, everyone has continuously asked the same basic question:
“Why is it when I try to bind my data source to SelectedDate, I get the error ‘The type DBNull cannot be converted to the type DateTime’? How can I bind it to this field?”
So the answer is, well you have to make a method call to see if the value is NULL, and return DateTime.MinValue instead. Wow, it seems so simple – this is where I believe the design flaw comes in…if it’s so darn simple, why do I keep getting asked the same question?
So, obviously, with the advancements in .NET 2.0, and the introduction of Nullable<T>, I have the opportunity to nick this in the butt so I don’t have to field this question so often. However, this would require a huge breaking change from the current version to Server Controls v2.0 in the sense that SelectedDate / SelectedTime would now become Nullable<DateTime>.
Now, if you know your CLR internals well enough, typeof(Nullable<DateTime>) != typeof(DateTime). This means that existing code where you could do .SelectedDate.ToShortDateString() no longer “just works” because you have to take it 1 step further: .SelectedDate.Value.ToShortDateString().
So, being that I develop the controls for the community, how big of a hit would it be if modifying the current signature of SelectedDate / SelectedTime to be Nullable<DateTime>? Let me know by utilizing the comment’s feature to leave your vote. Thanks, and I appreciate your honesty.
Are you living under a rock? No? Did you see that Excentrics World Server Controls v2.0, RC1 is out in public? Check it out!
I’m proud to announce the public release of Excentrics World Server Controls v2.0, RC1! With a complete rewrite from .NET 1.1 to .NET 2.0, over 120 bug fixes or new additions, 2 alpha releases, 2 beta releases, and full reimplemented design-time support, it’s been a long time in the waiting for all! Today marks the day that Excentrics World moves into vNext.
So, if you’re interested in test-driving, great! Excentrics World is looking for the public to help flush out any of the final kink’s prior to Server Controls v2.0 goes RTM.
Thanks again to all of my beta testers! Enjoy the release candidate community!