>>Is it a property or a field?
>
>Well, to me it has always been a property. But, if you are talking about the Get/Set approach, no I am not using such an approach. Is this what defines a property? So, that would mean the current definition I have is a field?

Michel,

As Bonnie pointed out, it's a field. .NET supports both properties and fields and they're not the same thing. Admittedly, I'm still trying to figure out the difference and when to use each.