Usage Warnings

 

The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.

The latest version of this topic can be found at Usage Warnings.

Usage warnings support proper usage of the .NET Framework.

RuleDescription
CA1801: Review unused parametersA method signature includes a parameter that is not used in the method body.
CA1806: Do not ignore method resultsA new object is created but never used; or a method that creates and returns a new string is called and the new string is never used; or a COM or P/Invoke method returns an HRESULT or error code that is never used.
CA1816: Call GC.SuppressFinalize correctlyA method that is an implementation of Dispose does not call GC.SuppressFinalize; or a method that is not an implementation of Dispose calls GC.SuppressFinalize; or a method calls GC.SuppressFinalize and passes something other than this (Me in Visual Basic).
CA2200: Rethrow to preserve stack detailsAn exception is re-thrown and the exception is explicitly specified in the throw statement. If an exception is re-thrown by specifying the exception in the throw statement, the list of method calls between the original method that threw the exception and the current method is lost.
CA2201: Do not raise reserved exception typesThis makes the original error hard to detect and debug.
CA2202: Do not dispose objects multiple timesA method implementation contains code paths that could cause multiple calls to System.IDisposable.Dispose or a Dispose equivalent (such as a Close() method on some types) on the same object.
CA2204: Literals should be spelled correctlyA literal string in a method body contains one or more words that are not recognized by the Microsoft spelling checker library.
CA2205: Use managed equivalents of Win32 APIA platform invoke method is defined and a method with the equivalent functionality exists in the .NET Framework class library.
CA2207: Initialize value type static fields inlineA value type declares an explicit static constructor. To fix a violation of this rule, initialize all static data when it is declared and remove the static constructor.
CA2208: Instantiate argument exceptions correctlyA call is made to the default (parameterless) constructor of an exception type that is or derives from ArgumentException, or an incorrect string argument is passed to a parameterized constructor of an exception type that is or derives from ArgumentException.
CA2211: Non-constant fields should not be visibleStatic fields that are neither constants nor read-only are not thread-safe. Access to such a field must be carefully controlled and requires advanced programming techniques for synchronizing access to the class object.
CA2212: Do not mark serviced components with WebMethodA method in a type that inherits from System.EnterpriseServices.ServicedComponent is marked with System.Web.Services.WebMethodAttribute. Because WebMethodAttribute and a ServicedComponent method have conflicting behavior and requirements for context and transaction flow, the behavior of the method will be incorrect in some scenarios.
CA2213: Disposable fields should be disposedA type that implements System.IDisposable declares fields that are of types that also implement IDisposable. The Dispose method of the field is not called by the Dispose method of the declaring type.
CA2214: Do not call overridable methods in constructorsWhen a constructor calls a virtual method, it is possible that the constructor for the instance that invokes the method has not executed.
CA2215: Dispose methods should call base class disposeIf a type inherits from a disposable type, it must call the Dispose method of the base type from its own Dispose method.
CA2216: Disposable types should declare finalizerA type that implements System.IDisposable, and has fields that suggest the use of unmanaged resources, does not implement a finalizer as described by Object.Finalize.
CA2217: Do not mark enums with FlagsAttributeAn externally visible enumeration is marked with FlagsAttribute, and it has one or more values that are not powers of two or a combination of the other defined values on the enumeration.
CA2218: Override GetHashCode on overriding EqualsGetHashCode returns a value, based on the current instance, that is suited for hashing algorithms and data structures such as a hash table. Two objects that are the same type and are equal must return the same hash code.
CA2219: Do not raise exceptions in exception clausesWhen an exception is raised in a finally or fault clause, the new exception hides the active exception. When an exception is raised in a filter clause, the run time silently catches the exception. This makes the original error hard to detect and debug.
CA2220: Finalizers should call base class finalizerFinalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method.
CA2221: Finalizers should be protectedFinalizers must use the family access modifier.
CA2222: Do not decrease inherited member visibilityYou should not change the access modifier for inherited members. Changing an inherited member to private does not prevent callers from accessing the base class implementation of the method.
CA2223: Members should differ by more than return typeAlthough the common language runtime allows the use of return types to differentiate between otherwise identical members, this feature is not in the Common Language Specification, nor is it a common feature of .NET programming languages.
CA2224: Override equals on overloading operator equalsA public type implements the equality operator, but does not override Object.Equals.
CA2225: Operator overloads have named alternatesAn operator overload was detected, and the expected named alternative method was not found. The named alternative member provides access to the same functionality as the operator, and is provided for developers who program in languages that do not support overloaded operators.
CA2226: Operators should have symmetrical overloadsA type implements the equality or inequality operator, and does not implement the opposite operator.
CA2227: Collection properties should be read onlyA writable collection property allows a user to replace the collection with a different collection. A read-only property stops the collection from being replaced but still allows the individual members to be set.
CA2228: Do not ship unreleased resource formatsResource files that were built by using pre-release versions of the .NET Framework might not be usable by supported versions of the .NET Framework.
CA2229: Implement serialization constructorsTo fix a violation of this rule, implement the serialization constructor. For a sealed class, make the constructor private; otherwise, make it protected.
CA2230: Use params for variable argumentsA public or protected type contains a public or protected method that uses the VarArgs calling convention instead of the params keyword.
CA2231: Overload operator equals on overriding ValueType.EqualsA value type overrides Object.Equals but does not implement the equality operator.
CA2232: Mark Windows Forms entry points with STAThreadSTAThreadAttribute indicates that the COM threading model for the application is a single-threaded apartment. This attribute must be present on the entry point of any application that uses Windows Forms; if it is omitted, the Windows components might not work correctly.
CA2233: Operations should not overflowArithmetic operations should not be performed without first validating the operands, to make sure that the result of the operation is not outside the range of possible values for the data types involved.
CA2234: Pass System.Uri objects instead of stringsA call is made to a method that has a string parameter whose name contains "uri", "URI", "urn", "URN", "url", or "URL". The declaring type of the method contains a corresponding method overload that has a System.Uri parameter.
CA2235: Mark all non-serializable fieldsAn instance field of a type that is not serializable is declared in a type that is serializable.
CA2236: Call base class methods on ISerializable typesTo fix a violation of this rule, call the base type GetObjectData method or serialization constructor from the corresponding derived type method or constructor.
CA2237: Mark ISerializable types with SerializableAttributeTo be recognized by the common language runtime as serializable, types must be marked with the SerializableAttribute attribute even if the type uses a custom serialization routine through implementation of the ISerializable interface.
CA2238: Implement serialization methods correctlyA method that handles a serialization event does not have the correct signature, return type, or visibility.
CA2239: Provide deserialization methods for optional fieldsA type has a field that is marked with the System.Runtime.Serialization.OptionalFieldAttribute attribute, and the type does not provide de-serialization event handling methods.
CA2240: Implement ISerializable correctlyTo fix a violation of this rule, make the GetObjectData method visible and overridable, and make sure that all instance fields are included in the serialization process or explicitly marked with the NonSerializedAttribute attribute.
CA2241: Provide correct arguments to formatting methodsThe format argument passed to System.String.Format does not contain a format item that corresponds to each object argument, or vice versa.
CA2242: Test for NaN correctlyThis expression tests a value against Single.Nan or Double.Nan. Use Single.IsNan(Single) or Double.IsNan(Double) to test the value.
CA2243: Attribute string literals should parse correctlyAn attribute's string literal parameter does not parse correctly for a URL, a GUID, or a version.
Show: