Michel,

It's not that it's *wrong*, meaning it won't work ... but since it's not necessary to do, then it's simply redundant and I doubt if it makes it any clearer to the developer as to what is going on.

~~Bonnie


>>It's not wrong but it's not the proper way acording to that guideline.
>>I think there they mean new Collection() creates a Collection type already and no need to explicitly specify type. I wouldn't agree to those guidelines if I were a VB.Net coder, I'm not and I don't care:)
>
>Yes, my question was mostly to know if those guidelines are ok. For me, I always declare the type and the value. So, this is a better representation of the type of the property and its default value. It is much easier for a developer to follow. It surprised me when I saw that on their Web site.