Static fields should be constant unless you carefully manage access to the field using locks. Using static variables without making them thread safe can compromise execution state. This rule applies to managed code libraries. If the analyzed assembly is an application, it is usually safe to exclude violations of this rule.
StatementLambdasSample : Statement lambdas allow you to declare procedures with multiple statements inside other procedures ...
Statements that contain CREATE SCHEMA AUTHORIZATION but do not specify a name are permitted for backward compatibility only. ...
Static 'val' fields in types must be mutable, private and marked with the '[ ]' attribute. They are initialized to the 'null' ...
Static Content has not been configured in Internet Information Services (IIS). If you continue, it will be configured for ...
Static fields should be constant unless you carefully manage access to the field using locks. Using static variables without ...
Static fields should be initialized when declared. Initializing static data in explicit static constructors results in less ...
Static holder types do not provide functionality that derived instances can extend. Inheriting from such a type indicates ...
Static keyword Specifies that one or more declared local variables are to remain in existence and retain their latest values ...
Statically link the given assembly and all referenced DLLs that depend on this assembly. Use an assembly name e.g. mylib, ...