CA1822: Mark members as static
|Fix is breaking or non-breaking||Non-breaking - If the member is not visible outside the assembly, regardless of the change you make.
Non-breaking - If you just change the member to an instance member with the
Breaking - If you change the member from an instance member to a static member and it is visible outside the assembly.
A member that does not access instance data is not marked as static (Shared in Visual Basic).
Members that do not access instance data or call instance methods can be marked as static (Shared in Visual Basic). After you mark the methods as static, the compiler will emit nonvirtual call sites to these members. Emitting nonvirtual call sites will prevent a check at run time for each call that makes sure that the current object pointer is non-null. This can achieve a measurable performance gain for performance-sensitive code. In some cases, the failure to access the current object instance represents a correctness issue.
How to fix violations
Mark the member as static (or Shared in Visual Basic) or use 'this'/'Me' in the method body, if appropriate.
When to suppress warnings
It is safe to suppress a warning from this rule for previously shipped code for which the fix would be a breaking change.
You can configure which parts of your codebase to run this rule on, based on their accessibility. For example, to specify that the rule should run only against the non-public API surface, add the following key-value pair to an .editorconfig file in your project:
dotnet_code_quality.ca1822.api_surface = private, internal
You can configure this option for just this rule, for all rules, or for all rules in this category (Performance). For more information, see Code quality rule configuration options.