>I find most .NET language programmers avoid our Foxpro habit of indicating data type with a prefix. I guess with strong typing and intellisense it is a lot less necessary.
>
>By now I've trained myself to avoid using type, class, object etc as field names of any kind. Just more trouble than it is worth. ( broke the "class" habit in VFP as I was writing a lot of school software - started using "course" ) Best way seems to be to extend the word - ActionType, AcademicClass etc.

But class and course are not the same thing, at least in our jargon (I wrote a now defunct system for our training department and a class is an instance of a course) , I prefer your second example, extending the word, of course knowing me the first word would be always the same... Fu..ing (Fu..ingType, Fuc..ingClass) :)