Hello,
As we use Nullable<int> or int? we have databinding issues, maybe it might be a WPF learning-curve where we need to impliment an convertor on every xaml. I hope not :)
But what about SmartInt, SmartBool and so on.
I looked on CSLA Contrib but those sources are build against an old CSLA version. Heck, they aren't implimenting IMobileObject etc.
Is it doable to build this into something global in WPF?
Or is it smarter to use a SmartInt32 IFieldData
PS: I could join the CSLA Contrib team and impliment those myself hehe.
Rocky,
1) Where does the IMobileObject interface stand for?
I know it's for supporting serialization by the MobileFormater.
The current SmartInt32 in CSLAContrib wont work then i guess.
The SmartData has an TypeConverter, i guess that is for WPF?
Greetings,
Raymond
PS:
Whoever is "the product owner" of CSLAContrib should say if CSLAContrib continues to CSLA 3.6 (meaning 3.5 .net FW with SP1)
There is no formal “product owner” of CSLAcontrib. Various
people who’ve had good ideas and/or time to implement them have put
things in there, but there’s never been an overall coordinator.
IMobileObject is the interface required by the MobileFormatter.
Any non-primitive value that needs to serialize to/from Silverlight must
implement IMobileObject.
SmartDate, in 3.6, is finally a complete data type (I think). What
I mean by this, is that it finally acts like a true value type – just like
DateTime, etc. There’s a ton of code in SmartDate that is there only to
make it play well with .NET – including the type converter. That converter
isn’t for WPF, it is for .NET in general and covers a scenario where a
cast won’t work (I don’t recall specifically – either Windows
Forms or Web Forms data binding needed it).
Over the past few years I’ve learned that creating a
really smooth value type requires a LOT of work!
Rocky
From: rfcdejong
[mailto:cslanet@lhotka.net]
Sent: Thursday, February 19, 2009 7:07 AM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] SmartInt, SmartBool, SmartStuff
Rocky,
1) Where does the IMobileObject interface stand for?
I know it's for supporting serialization by the MobileFormater.
The current SmartInt32 in CSLAContrib wont work then i guess.
The SmartData has an TypeConverter, i guess that is for WPF?
Greetings,
Raymond
PS:
Whoever is "the product owner" of CSLAContrib should say if
CSLAContrib continues to CSLA 3.6 (meaning 3.5 .net FW with SP1)
Copyright (c) Marimer LLC