Flagging complex properties as Browsable in the compact framework
Posted
by Rowland Shaw
on Stack Overflow
See other posts from Stack Overflow
or by Rowland Shaw
Published on 2010-03-27T22:05:57Z
Indexed on
2010/03/27
22:13 UTC
Read the original article
Hit count: 244
I'm working on a compact framework project and whilst most of the properties are fairly straight forward (I.e. mark them as browsable in the xmta file), I'm struggling to get this to work for more complex types - on the full framework, I'd just implement a custom TypeConverter
and go from there, but it seems the CF TypeConverter
doesn't have any of the type converting methods to override, which has left me a little stuck?
It probably should be blindingly obvious but how would I go about supporting design time property support for more complex types (for the sake of argument, assume I can already convert to and from a string, but I'd prefer to keep this strongly typed, rather than just pretend it was a string and parse it both ways. Where should I be looking to achieve this?
© Stack Overflow or respective owner