Mike,

Is it a name I'd use? No.

But it's a perfectly valid property name for any object that has a number of things. If it wasn't why would someone like Microsoft use it for every collection class it's ever created?

And as long as the class is properly documented there shouldn't be too much hidden (or private or protected *s*) below the surface that will bite you.

>If someone created a class with a property named Count, I wouldn't care what kind of results their class gave me ;-) That would probably be the tip of the iceberg as far as unexpected behavior.