CA1812: Avoid uninstantiated internal classes
| Value | |
|---|---|
| Rule ID | CA1812 |
| Category | Performance |
| Fix is breaking or non-breaking | Non-breaking |
Cause
An internal (assembly-level) type is never instantiated.
Rule description
This rule tries to locate a call to one of the constructors of the type and reports a violation if no call is found.
The following types are not examined by this rule:
Value types
Abstract types
Enumerations
Delegates
Compiler-emitted array types
Types that cannot be instantiated and that only define
static(Sharedin Visual Basic) methods.
If you apply the System.Runtime.CompilerServices.InternalsVisibleToAttribute to the assembly that's being analyzed, this rule will not flag types that are marked as internal (Friend in Visual Basic) because a field may be used by a friend assembly.
How to fix violations
To fix a violation of this rule, remove the type or add code that uses it. If the type contains only static methods, add one of the following to the type to prevent the compiler from emitting a default public instance constructor:
The
staticmodifier for C# types that target .NET Framework 2.0 or later.A private constructor for types that target .NET Framework versions 1.0 and 1.1.
When to suppress warnings
It is safe to suppress a warning from this rule. We recommend that you suppress this warning in the following situations:
The class is created through late-bound reflection methods such as System.Activator.CreateInstance.
The class is registered in an inversion of control (IoC) container as part of the dependency injection pattern.
The class is created automatically by the runtime or ASP.NET. Some examples of automatically created classes are those that implement System.Configuration.IConfigurationSectionHandler or System.Web.IHttpHandler.
The class is used as a type parameter in a class definition and has a
newconstraint. The following example will be flagged by rule CA1812:internal class MyClass { public void DoSomething() { } } public class MyGeneric<T> where T : new() { public T Create() { return new T(); } } MyGeneric<MyClass> mc = new MyGeneric<MyClass>(); mc.Create();
Suppress a warning
If you just want to suppress a single violation, add preprocessor directives to your source file to disable and then re-enable the rule.
#pragma warning disable CA1812
// The code that's violating the rule is on this line.
#pragma warning restore CA1812
To disable the rule for a file, folder, or project, set its severity to none in the configuration file.
[*.{cs,vb}]
dotnet_diagnostic.CA1812.severity = none
To disable this entire category of rules, set the severity for the category to none in the configuration file.
[*.{cs,vb}]
dotnet_analyzer_diagnostic.category-Performance.severity = none
For more information, see How to suppress code analysis warnings.
Related rules
Povratne informacije
Pošalјite i prikažite povratne informacije za