S
Sahil Malik
I have no alternate way of reaching the MS product team, so I am using this
newsgroup - hopefully the MS gods will pick it up from here.
The suggestion is - UDTs are a very useful feature. However the rules
surrounding the Format.Native, vs. Format.UserDefined are way too hairy.
They are understandbly so, because well thats just how life is. But for a
DBA who is traditionally not a CLR developer he will probably get
befuddulled by the hairiness. Could we use OOP to encapsulate atleast some
of those rules? My initial thoughts are centered around creating two base
classes for either Format.Native, and Format.UserDefined .. and take it from
there.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
newsgroup - hopefully the MS gods will pick it up from here.
The suggestion is - UDTs are a very useful feature. However the rules
surrounding the Format.Native, vs. Format.UserDefined are way too hairy.
They are understandbly so, because well thats just how life is. But for a
DBA who is traditionally not a CLR developer he will probably get
befuddulled by the hairiness. Could we use OOP to encapsulate atleast some
of those rules? My initial thoughts are centered around creating two base
classes for either Format.Native, and Format.UserDefined .. and take it from
there.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik