United States (English)

Home Library Learn Samples Downloads Support Community Forums

MSDN Library

Development Tools and Languages

Visual Studio 2012

Application Development in Visual Studio

Quality and Diagnostic Tools

Analyzing Application Quality

Analyzing Managed Code Quality

Code Analysis for Managed Code Warnings

Performance Warnings

CA1800: Do not cast unnecessarily

CA1802: Use Literals Where Appropriate

CA1804: Remove unused locals

CA1809: Avoid excessive locals

CA1810: Initialize reference type static fields inline

CA1811: Avoid uncalled private code

CA1812: Avoid uninstantiated internal classes

CA1813: Avoid unsealed attributes

CA1814: Prefer jagged arrays over multidimensional

CA1815: Override equals and operator equals on value types

CA1819: Properties should not return arrays

CA1820: Test for empty strings using string length

CA1821: Remove empty finalizers

CA1822: Mark members as static

CA1823: Avoid unused private fields

CA1824: Mark assemblies with NeutralResourcesLanguageAttribute

Minimize

0 out of 1 rated this helpful - Rate this topic

CA1823: Avoid unused private fields

Visual Studio 2012

TypeName	AvoidUnusedPrivateFields
CheckId	CA1823
Category	Microsoft.Performance
Breaking Change	Non-breaking

This rule is reported when a private field in your code exists but is not used by any code path.

Rule Description

Private fields were detected that do not appear to be accessed in the assembly.

How to Fix Violations

To fix a violation of this rule, remove the field or add code that uses it.

When to Suppress Warnings

It is safe to suppress a warning from this rule.

CA1812: Avoid uninstantiated internal classes

CA1801: Review unused parameters

CA1804: Remove unused locals

CA1811: Avoid uncalled private code

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

© 2013 Microsoft. All rights reserved.