Managed Recommended Rules rule set for managed code
Use the Microsoft Managed Recommended Rules rule set to focus on the most critical problems in your managed code, including potential security holes, application crashes, and other important logic and design errors. This rule set includes all the rules in the Managed Minimum Rules rule set.
Include this rule set in any custom rule set that you create for your projects.
| Rule | Description |
|---|---|
| CA1001 | Types that own disposable fields should be disposable |
| CA1009 | Declare event handlers correctly |
| CA1016 | Mark assemblies with AssemblyVersionAttribute |
| CA1033 | Interface methods should be callable by child types |
| CA1049 | Types that own native resources should be disposable |
| CA1060 | Move P/Invokes to NativeMethods class |
| CA1061 | Do not hide base class methods |
| CA1063 | Implement IDisposable correctly |
| CA1065 | Do not raise exceptions in unexpected locations |
| CA1301 | Avoid duplicate accelerators |
| CA1400 | P/Invoke entry points should exist |
| CA1401 | P/Invokes should not be visible |
| CA1403 | Auto layout types should not be COM visible |
| CA1404 | Call GetLastError immediately after P/Invoke |
| CA1405 | COM visible type base types should be COM visible |
| CA1410 | COM registration methods should be matched |
| CA1415 | Declare P/Invokes correctly |
| CA1821 | Remove empty finalizers |
| CA1900 | Value type fields should be portable |
| CA1901 | P/Invoke declarations should be portable |
| CA2002 | Do not lock on objects with weak identity |
| CA2100 | Review SQL queries for security vulnerabilities |
| CA2101 | Specify marshaling for P/Invoke string arguments |
| CA2108 | Review declarative security on value types |
| CA2111 | Pointers should not be visible |
| CA2112 | Secured types should not expose fields |
| CA2114 | Method security should be a superset of type |
| CA2116 | APTCA methods should only call APTCA methods |
| CA2117 | APTCA types should only extend APTCA base types |
| CA2122 | Do not indirectly expose methods with link demands |
| CA2123 | Override link demands should be identical to base |
| CA2124 | Wrap vulnerable finally clauses in outer try |
| CA2126 | Type link demands require inheritance demands |
| CA2131 | Security critical types may not participate in type equivalence |
| CA2132 | Default constructors must be at least as critical as base type default constructors |
| CA2133 | Delegates must bind to methods with consistent transparency |
| CA2134 | Methods must keep consistent transparency when overriding base methods |
| CA2137 | Transparent methods must contain only verifiable IL |
| CA2138 | Transparent methods must not call methods with the SuppressUnmanagedCodeSecurity attribute |
| CA2140 | Transparent code must not reference security critical items |
| CA2141 | Transparent methods must not satisfy LinkDemands |
| CA2146 | Types must be at least as critical as their base types and interfaces |
| CA2147 | Transparent methods may not use security asserts |
| CA2149 | Transparent methods must not call into native code |
| CA2200 | Rethrow to preserve stack details |
| CA2202 | Do not dispose objects multiple times |
| CA2207 | Initialize value type static fields inline |
| CA2212 | Do not mark serviced components with WebMethod |
| CA2213 | Disposable fields should be disposed |
| CA2214 | Do not call overridable methods in constructors |
| CA2216 | Disposable types should declare finalizer |
| CA2220 | Finalizers should call base class finalizer |
| CA2229 | Implement serialization constructors |
| CA2231 | Overload operator equals on overriding ValueType.Equals |
| CA2232 | Mark Windows Forms entry points with STAThread |
| CA2235 | Mark all non-serializable fields |
| CA2236 | Call base class methods on ISerializable types |
| CA2237 | Mark ISerializable types with SerializableAttribute |
| CA2238 | Implement serialization methods correctly |
| CA2240 | Implement ISerializable correctly |
| CA2241 | Provide correct arguments to formatting methods |
| CA2242 | Test for NaN correctly |