Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Back in my COM days, it was common to use the I in interface names as a personal pronoun, as if the object was describing what it could do. ie:
IProvideData
Is this still the case in the world of .Net, or it is now preffered to use the third person:
IDataProvider
Quoted from the naming guidelines:
Given that,
IDataProviderseems like a better name thanIProvideData. I find it more logical, especially when paired with member names.IDataProvider.GetDataseems more natural to me thanIProvideData.GetData.Read more in Names of Classes, Structs, and Interfaces in the Design Guidelines for Developing Class Libraries.