Warning / Error

Number

Description

Visual Studio 2008 Team System

Visual Studio 2010 Premium

CA0051

No rules were selected.

Yes

Yes

CA0053

Rule assembly could not be loaded.

Yes

Yes

CA0055

Could not load file:<path>

Yes

Yes

CA0057

Violations cannot be mapped to the current set of targets and rules.

Yes

Yes

CA0059

Command line switch error.

Yes

Yes

CA0061

The rule 'RuleId' referenced in rule set 'RuleSetName' could not be found.

-

Yes

CA0063

Failed to load rule set file or one of its dependent rule set files.

Yes

CA0065

Unsupported metadata construct: Type 'TypeName' contains both a property and a field with the same name 'PropertyFieldName'

Yes

CA0067

Directory not found.

Yes

CA0069

UsingAlternatePlatform. FrameworkVersion1 could not be found. Using FrameworkVersion2 instead. For best analysis results please ensure that the correct .NET Framework is installed.

Yes

CA0501

Unable to read output report.

Yes

Yes

CA0503

Additional warnings cannot be displayed.

Yes

Yes

CA0505

The property is deprectated. Use the superceding property

Yes

CA1001

Types that own disposable fields should be disposable

Yes

Yes

CA1003

Use generic event handler instances

Yes

Yes

CA1005

Avoid excessive parameters on generic types

Yes

Yes

CA1007

Use generics where appropriate

Yes

Yes

CA1009

Declare event handlers correctly

Yes

Yes

CA1011

Consider passing base types as parameters

Yes

Yes

CA1013

Overload operator equals on overloading add and subtract

Yes

Yes

CA1016

Mark assemblies with AssemblyVersionAttribute

Yes

Yes

CA1018

Mark attributes with AttributeUsageAttribute

Yes

Yes

CA1020

Avoid namespaces with few types

Yes

Yes

CA1023

Indexers should not be multidimensional

Yes

Yes

CA1025

Replace repetitive arguments with params array

Yes

Yes

CA1027

Mark enums with FlagsAttribute

Yes

Yes

CA1030

Use events where appropriate

Yes

Yes

CA1032

Implement standard exception constructors

Yes

Yes

CA1034

Nested types should not be visible

Yes

Yes

CA1036

Override methods on comparable types

Yes

Yes

CA1039

Lists are strongly typed

Yes

Yes

CA1041

Provide ObsoleteAttribute message

Yes

Yes

CA1044

Properties should not be write only

Yes

Yes

CA1046

Do not overload operator equals on reference types

Yes

Yes

CA1048

Do not declare virtual members in sealed types

Yes

Yes

CA1050

Declare types in namespaces

Yes

Yes

CA1052

Static holder types should be sealed

Yes

Yes

CA1054

URI parameters should not be strings

Yes

Yes

CA1056

URI properties should not be strings

Yes

Yes

CA1058

Types should not extend certain base types

Yes

Yes

CA1060

Move P/Invokes to NativeMethods class

Yes

Yes

CA1062

Validate arguments of public methods

Yes

CA1064

Exceptions should be public

Yes

Yes

CA1300

Specify MessageBoxOptions

Yes

Yes

CA1302

Do not hardcode locale specific strings

Yes

Yes

CA1304

Specify CultureInfo

Yes

Yes

CA1306

Set locale for data types

Yes

Yes

CA1308

Normalize strings to uppercase

Yes

Yes

CA1400

P/Invoke entry points should exist

Yes

Yes

CA1402

Avoid overloads in COM visible interfaces

Yes

Yes

CA1404

Call GetLastError immediately after P/Invoke

Yes

Yes

CA1406

Avoid Int64 arguments for Visual Basic 6 clients

Yes

Yes

CA1408

Do not use AutoDual ClassInterfaceType

Yes

Yes

CA1410

COM registration methods should be matched

Yes

Yes

CA1412

Mark ComSource interfaces as IDispatch

Yes

Yes

CA1414

Mark boolean P/Invoke arguments with MarshalAs

Yes

Yes

CA1500

Variable names should not match field names

Yes

Yes

CA1501

Avoid excessive inheritance

Yes

Yes

CA1502

Avoid excessive complexity

Yes

Yes

CA1504

Review misleading field names

Yes

Yes

CA1505

Avoid unmaintainable code

Yes

Yes

CA1506

Avoid excessive class coupling

Yes

Yes

CA1600

Do not use idle process priority

Yes

Yes

CA1700

Do not name enum values 'Reserved'

Yes

Yes

CA1702

Compound words should be cased correctly

Yes

Yes

CA1704

Identifiers should be spelled correctly

Yes

Yes

CA1708

Identifiers should differ by more than case

Yes

Yes

CA1710

Identifiers should have correct suffix

Yes

Yes

CA1712

Do not prefix enum values with type name

Yes

Yes

CA1714

Flags enums should have plural names

Yes

Yes

CA1716

Identifiers should not match keywords

Yes

Yes

CA1719

Parameter names should not match member names

Yes

Yes

CA1721

Property names should not match get methods

Yes

Yes

CA1724

Type names should not match namespaces

Yes

Yes

CA1726

Use preferred terms

Yes

Yes

CA1801

Review unused parameters

Yes

Yes

CA1804

Remove unused locals

Yes

Yes

CA1806

Do not ignore method results

Yes

Yes

CA1810

Initialize reference type static fields inline

Yes

Yes

CA1812

Avoid uninstantiated internal classes

Yes

Yes

CA1814

Prefer jagged arrays over multidimensional

Yes

Yes

CA1816

Call GC.SuppressFinalize correctly

Yes

Yes

CA1820

Test for empty strings using string length

Yes

Yes

CA1822

Mark members as static

Yes

Yes

CA1824

Mark assemblies with NeutralResourcesLanguageAttribute

Yes

Yes

CA1901

P/Invoke declarations should be portable

Yes

Yes

CA2000

Dispose objects before losing scope

-

Yes

CA2002

Do not lock on objects with weak identity

Yes

Yes

CA2004

Remove calls to GC.KeepAlive

Yes

Yes

CA2100

Review SQL queries for security vulnerabilities

-

Yes

CA2102

Catch non-CLSCompliant exceptions in general handlers

Yes

Yes

CA2104

Do not declare read only mutable reference types

Yes

Yes

CA2106

Secure asserts

Yes

Yes

CA2108

Review declarative security on value types

Yes

Yes

CA2111

Pointers should not be visible

Yes

Yes

CA2114

Method security should be a superset of type

Yes

Yes

CA2116

APTCA methods should only call APTCA methods

Yes

Yes

CA2118

Review SuppressUnmanagedCodeSecurityAttribute usage

Yes

Yes

CA2120

Secure serialization constructors

Yes

Yes

CA2122

Do not indirectly expose methods with link demands

Yes

Yes

CA2124

Wrap vulnerable finally clauses in outer try

Yes

Yes

CA2127

Security transparent assemblies should not contain security critical code

Yes

No

CA2129

Security transparent code should not reference non-public security critical members

Yes

No

CA2131

Security critical types may not participate in type equivalence

-

Yes

CA2133

Delegates must bind to methods with consistent transparency

-

Yes

CA2135

Level 2 assemblies should not contain LinkDemands

-

Yes

CA2137

Transparent methods must contain only verifiable IL

-

Yes

CA2139

Transparent methods may not use the HandleProcessCorruptingExceptions attribute

-

Yes

CA2141

Transparent methods must not satisfy LinkDemands

-

Yes

CA2143

Transparent methods should not use security demands

-

Yes

CA2145

Transparent methods should not be decorated with the SuppressUnmanagedCodeSecurityAttribute

-

Yes

CA2147

Transparent methods may not use security asserts

-

Yes

CA2200

Rethrow to preserve stack details

Yes

Yes

CA2202

Do not dispose objects multiple times

-

Yes

CA2205

Use managed equivalents of Win32 API

Yes

Yes

CA2208

Instantiate argument exceptions correctly

Yes

Yes

CA2211

Non-constant fields should not be visible

Yes

Yes

CA2213

Disposable fields should be disposed

Yes

Yes

CA2215

Dispose methods should call base class dispose

-

Yes

CA2217

Do not mark enums with FlagsAttribute

Yes

Yes

CA2219

Do not raise exceptions in exception clauses

Yes

Yes

CA2221

Finalizers should be protected

Yes

Yes

CA2223

Members should differ by more than return type

Yes

Yes

CA2225

Operator overloads have named alternates

Yes

Yes

CA2227

Collection properties should be read only

Yes

Yes

CA2229

Implement serialization constructors

Yes

Yes

CA2231

Overload operator equals on overriding ValueType.Equals

Yes

Yes

CA2233

Operations should not overflow

Yes

Yes

CA2235

Mark all non-serializable fields

Yes

Yes

CA2237

Mark ISerializable types with SerializableAttribute

Yes

Yes

CA2239

Provide deserialization methods for optional fields

Yes

Yes

CA2241

Provide correct arguments to formatting methods

-

Yes

CA2243

Attribute string literals should parse correctly

Yes

Yes

Warning / Error

Number

Description

Visual Studio Team System 2008

Visual Studio 2010 Premium

0x1

Analysis error

Yes

Yes

0x4

Project load error

Yes

Yes

0x10

Rule library load error

Yes

Yes

0x40

Output error

Yes

Yes

0x100

Initialization error

Yes

Yes

0x400

BuildBreakingMessage

Yes

Yes

Warning / Error

Number

Description

Visual Studio Team System 2008

Visual Studio 2010 Premium

C6011

dereferencing NULL pointer <name>

Yes

Yes

C6031

return value ignored: <function> could return unexpected value

Yes

Yes

C6054

string <variable> may not be zero-terminated

Yes

Yes

C6059

Incorrect length parameter in call to <function>. Pass the number of remaining characters, not the buffer size of <variable>

Yes

Yes

C6064

missing integer argument to <function> corresponding to conversion specifier <number>

Yes

Yes

C6067

parameter <number> in call to <function> must be the address of the string

Yes

Yes

C6201

buffer overrun for <variable>, which is possibly stack allocated: index <name> is out of valid index range <min> to <max>

Yes

Yes

C6203

buffer overrun for buffer <variable> in call to <function>: length <size> exceeds buffer size

Yes

Yes

C6209

using 'sizeof<variable1>' as parameter <number> in call to <function> where <variable2> may be an array of wide characters, did you intend to use character count rather than byte count?

Yes

Yes

C6214

cast between semantically different integer types: HRESULT to a Boolean type

Yes

Yes

C6216

compiler-inserted cast between semantically different integral types: a Boolean type to HRESULT

Yes

Yes

C6219

Implicit cast between semantically different integer types: comparing HRESULT to 1 or TRUE. Consider using SUCCEEDED or FAILED macro instead

Yes

Yes

C6221

Implicit cast between semantically different integer types: comparing HRESULT to an integer. Consider using SUCCEEDED or FAILED macros instead

Yes

Yes

C6226

Implicit cast between semantically different integer types: assigning -1 to HRESULT. Consider using E_FAIL instead

Yes

Yes

C6235

(<non-zero constant> || <expression>) is always a non-zero constant

Yes

Yes

C6237

(<zero> && <expression>) is always zero. <expression> is never evaluated and may have side effects

Yes

Yes

C6240

(<expression> && <non-zero constant>) always evaluates to the result of <expression>. Did you intend to use the bitwise-and operator?

Yes

Yes

C6244

local declaration of <variable> hides previous declaration at <line> of <file>

Yes

Yes

C6248

setting a SECURITY_DESCRIPTOR’s DACL to NULL will result in an unprotected object

Yes

Yes

C6255

_alloca indicates failure by raising a stack overflow exception. Consider using _alloca_s instead

Yes

Yes

C6259

labeled code is unreachable: (<expression> & <constant>) in switch-expr cannot evaluate to <case-label>

Yes

Yes

C6262

Function uses <constant> bytes of stack: exceeds /analyze:stacksize<constant>. Consider moving some data to heap

Yes

Yes

C6268

Incorrect order of operations: (<TYPE1>)(<TYPE2>)x + y. Possible missing parentheses in (<TYPE1>)((<TYPE2>)x + y)

Yes

Yes

C6270

missing float argument to <function>: add a float argument corresponding to conversion specifier <number>

Yes

Yes

C6272

non-float passed as argument <number> when float is required in call to <function>

Yes

Yes

C6274

non-character passed as parameter <number> when character is required in call to <function>

Yes

Yes

C6277

NULL application name with an unquoted path in call to <function>: results in a security vulnerability if the path contains spaces

Yes

Yes

C6279

<variable> is allocated with scalar new, deleted with array delete []

Yes

Yes

C6281

warning 6281 - incorrect order of operations: relational operators have higher precedence than bitwise operators

Yes

Yes

C6283

<variable> is allocated with array new [], but deleted with scalar delete

Yes

Yes

C6285

(<non-zero constant> || <non-zero constant>) is always a non-zero constant. Did you intend to use the bitwise-and operator?

Yes

Yes

C6287

redundant code: the left and right sub-expressions are identical

Yes

Yes

C6289

Incorrect operator: mutual exclusion over || is always a non-zero constant. Did you intend to use && instead?

Yes

Yes

C6291

Bitwise operation on logical result: ! has higher precedence than |. Use || or (!(x | y)) instead

Yes

Yes

C6293

Ill-defined for-loop: counts down from minimum

Yes

Yes

C6295

Ill-defined for-loop: <variable> values are of the range "min" to "max". Loop executed indefinitely

Yes

Yes

C6297

Arithmetic overflow: 32-bit value is shifted, then cast to 64-bit value. Result may not be an expected value

Yes

Yes

C6299

explicitly comparing a bit field to a Boolean type will yield unexpected results

Yes

Yes

C6303

format string mismatch: wide character string passed as parameter <number> when character string is required in call to <function>

Yes

Yes

C6306

incorrect call to <function>: consider using <function> which accepts a va_list as an argument

Yes

Yes

C6309

argument <number> is null: it does not adhere to function specification of <function>

Yes

Yes

C6312

Possible infinite loop: use of the constant EXCEPTION_CONTINUE_EXECUTION in the exception-filter expression of a try-except

Yes

Yes

C6314

Incorrect order of operations: bitwise-or has higher precedence than the conditional-expression operator. Add parentheses to clarify intent

Yes

Yes

C6316

Incorrect operator: tested expression is constant and non-zero. Use bitwise-and to determine whether bits are set

Yes

Yes

C6318

Ill-defined __try/__except: use of the constant EXCEPTION_CONTINUE_SEARCH or another constant that evaluates to zero in the exception-filter expression. The code in the exception handler block is not executed

Yes

Yes

C6320

exception-filter expression is the constant EXCEPTION_EXECUTE_HANDLER. This may mask exceptions that were not intended to be handled

Yes

Yes

C6323

warning 6323 - use of arithmetic operator on Boolean type(s)

Yes

Yes

C6326

potential comparison of a constant with another constant

Yes

Yes

C6328

warning C6328:<type> passed as parameter <number> when <type> is required in call to <function>

Yes

Yes

C6332

Invalid parameter: passing zero as the dwFreeType parameter to <function> is not allowed. This results in the failure of this call

Yes

Yes

C6334

sizeof operator applied to an expression with an operator may yield unexpected results

Yes

Yes

C6336

arithmetic operator has precedence over question operator, use parentheses to clarify intent

Yes

Yes

C6383

buffer overrun due to conversion of an element count into a byte count: an element count is expected for parameter <number> in call to <function>

Yes

Yes

C6385

invalid data: accessing <buffer name>, the readable size is <size1> bytes, but <size2> bytes may be read: Lines: x, y

Yes

Yes

C6387

<argument> may be <value>: this does not adhere to the specification for the function <function name>: Lines: x, y

Yes

Yes

C6400

Using <function name> to perform a case-insensitive compare to constant string <string name>. Yields unexpected results in non-English locales

Yes

Yes

C6500

invalid annotation: value for <name> property is invalid

Yes

Yes

C6503

annotation conflict: references may not be marked Null=Yes or Null=Maybe

Yes

Yes

C6505

invalid annotation: MustCheck property may not be used on values of void type

Yes

Yes

C6507

annotation conflict: Null property at Deref=0 on a post condition must be a subset of the Null property on the precondition

Yes

Yes

C6509

invalid annotation: 'return' cannot be referenced from a precondition

Yes

Yes

C6511

invalid annotation: MustCheck property must be Yes or No

Yes

Yes

C6513

invalid annotation: ElementSizeConst requires additional size properties

Yes

Yes

C6515

warning C6515 - invalid annotation: <name> property may only be used on values of pointer type

Yes

Yes

C6517

annotation conflict: ValidElementsConst and ValidBytesConst may not be specified on the buffers that are not readable

Yes

Yes

C6521

invalid size specification: * operator can only be applied to pointer types

Yes

Yes

C6523

invalid size specification: parameter <name> not found

Yes

Yes

C6526

warning C6526 - invalid size specification: expression must be of array or pointer type

Yes

Yes

C6535

buffer cannot be of size <n>, bigger than max(size_t)

Yes

Yes