I am having trouble with FxCop warning CA1006, Microsoft.Design \"DoNotNestGenericTypesInMemberSignatures\". Specifically, I am designing a ReportCollection
I agree, another good time to ignore this rule is when you need to say:
Func>
of course you could use the non-generic IEnumerable, but then any type can be used as long as it implements IEnumerable (non-generic). The purpose of generics (in part) is to restrict the types that are permisable to a given set of types.
I think this rule is very stupid. only need it if you have multiple generic types nested. one layer of nesting is more than safe.
BTW, I think a lot of the LINQ Functions nest generic types as well, so if MS does it, we can too :)