Avoid using language-specific types name in parameters and members and data type identifiers in parameters. Types names might not be intuitive for all developers. It is recommended that you select a generic name, such as 'value', instead. If this is not sufficient, be sure to use the type name as it is defined in the .NET Framework Library and avoid language-specific type names completely. Some examples of C#-specific type names are 'float' (use 'Single' if a generic name is not sufficient), and 'ulong' (use 'UInt64' if a generic name is not sufficient).
Avoid API that require users to instantiate a generic type with another generic type as type argument. The syntax gets too ...
Avoid creating compound words from terms which exist in the dictionary as discrete terms. Do not create a compound word such ...
Avoid generic types with more than two type parameters as users have difficulties understanding what type parameters represent ...
Avoid naming an enum value 'Reserved'. Adding 'Reserved' values will lead to a breaking change on removal when the value ...
Avoid using language-specific types name in parameters and members and data type identifiers in parameters. Types names might ...
Axis object - Negative or zero values cannot be plotted correctly on logarithmic charts. Only positive values can be interpreted ...
BackgroundWorker component instance to manage the background thread. Can be created by dragging a BackgroundWorker component ...
Backing field for automatically implemented property '%1!ls!' must be fully assigned before control is returned to the caller. ...
Bad array declarator: To declare a managed array the rank specifier precedes the variable's identifier. To declare a fixed ...