> Using IClass naming is considered best practice in the .Net world AFAIK. No, it's the opposite. IClass is the norm, for legacy reasons going all the way back

> Using IClass naming is considered best practice in the .Net world AFAIK. No, it's the opposite. IClass is the norm, for legacy reasons going all the way back to the early COM days (it all started with IUnknown[1]). [1] https://msdn.microsoft.com/en-us/library/windows/desktop/ms680509(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...