All rules
CA1000Design Enabled by default: No

Do not declare static members on generic types

Do not declare static members on generic types

Microsoft docs

Description

When a static member of a generic type is called, the type argument must be specified for the type. When a generic instance member that does not support inference is called, the type argument must be specified for the member. The syntax for specifying the type argument in these two cases is different and easily confused, as the following calls demonstrate:

Generally, both of the prior declarations should be avoided so that the type argument does not have to be specified when the member is called. This results in a syntax for calling members in generics that is no different from the syntax for non-generics.

Cause

A generic type contains a static (Shared in Visual Basic) member.

By default, this rule only looks at externally visible types, but this is configurable.

How to fix violations

To fix a violation of this rule, remove the static member or change it to an instance member.

Example

// Static method in a generic type.
GenericType<int>.StaticMethod();

// Generic instance method that does not support inference.
someObject.GenericMethod<int>();

When to suppress

Do not suppress a warning from this rule. Providing generics in a syntax that is easy to understand and use reduces the time that is required to learn and increases the adoption rate of new libraries.

Group results
0 yes 0 no
ConsensusNone (disabled)
Severity preference (yes voters)
Suggestion0
Warning0
Error0