Generic Naming Convention // EnterpriseLibra ry way of doing things?

[sloan]

Is anyone else using the Microsoft Practices EnterpriseLibra ry conventions
for naming FILES (.cs) as far as a non-generic and generic implementation is
concerned?
Anyone have an alternative?
I brought this up a while back, but with this new thing I just saw, thought
I'd ask again.

See sample below from EnterpriseLibra ry

But it goes something like this.
ISomething.cs
ISomething.Gene ric.cs


IValidator.cs (filename of course)
namespace Microsoft.Pract ices.Enterprise Library.Validat ion
{
public interface Validator
{
ValidationResul ts Validate(object target);
void Validate(object target, ValidationResul ts validationResul ts);
}
}

IValidator.Gene ric.cs (filename of course)
namespace Microsoft.Pract ices.Enterprise Library.Validat ion
{
public interface Validator<T: Validator
{
ValidationResul ts Validate(T target);
void Validate(T target, ValidationResul ts validationResul ts);
}
}