> From: [email protected] [mailto:mono-list-
> [email protected]] On Behalf Of mimi
>
> public Dictionary<string,object> DictionaryField;
Unrelated to your actual question, it's recommended that you make public things
Properties instead of Fields.
public Dictionary<string,object> FooDict { get; set; }
This is basically because if you later need to add something like a set
accessor for data scrubbing or validation checking, by having a property, you
have not changed your interface. If you change a field to a property, it's
considered a breaking change - meaning - all your code and all the code that
depends on your code needs to be recompiled and the binaries are not compatible
with each other. If you want to know more, you can google for properties vs
fields. Lots of people have written things about it.
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
