Do not use names that require case sensitivity for uniqueness. Components must be fully usable from both case-sensitive and case-insensitive languages. Since case-insensitive languages cannot distinguish between two names within the same context that differ only by case, components must avoid this situation.
Do not nest type {0}. Alternatively, change its accessibility so that it is not externally visible. If this type is defined ...
Do not poll more often than or utilize timers that fire more frequently than once per second. Higher frequency periodic activity ...
Do not set process priority to Idle. Processes with System.Diagnostics.ProcessPriorityClass.Idle will occupy the CPU when ...
Do not use 'C' as a prefix for type names. Do not use any prefix for naming types. Consider using the name of the base class ...
Do not use names that require case sensitivity for uniqueness. Components must be fully usable from both case-sensitive and ...
Do not use public, protected or protected internal (Protected Friend) nested types as a way of grouping types. Use namespaces ...
Do not use string literals for system items that have locale-specific designations. Special system locations should be retrieved ...
Do not use the varargs calling convention to accept a variable number of arguments. In the managed world, the 'params' and ...
Do not use underscores when specifying identifiers. Some generated Visual Studio identifiers for applications contain underscore ...