Review parameters in non-virtual methods that are not used in the method body to ensure no correctness exists around failure to access them. Unused parameters incur maintenance and performance costs. Sometimes a violation of this rule can point to an implementation bug in the method (i.e. the parameter should actually have been used in the method body). Exclude warnings of this rule if the parameter has to exist because of backward compatibility.
Reverting to a SharePoint List View will reset the layout, formatting, and Web Part connections for the view. Existing connections ...
Review declarative security for {0} and its callers for potential vulnerabilities. The following call stack might expose ...
Review declarative security for {0} and its callers for potential vulnerabilities. This method is accessible from outside ...
Review field names which, by convention, appear to indicate they are instance or static but, in fact, are not. This rule ...
Review parameters in non-virtual methods that are not used in the method body to ensure no correctness exists around failure ...
Review the following for a possible security vulnerability: In {0}, the class member {1} is being passed to a {2} constructor. ...
Review the following for a possible security vulnerability: In {0}, the return value of a call to {1} is being passed to ...
Review the list of tasks the wizard has performed. Click Finish to complete the wizard or click Previous to make changes. ...
Review the query string passed to {0} in {1} for possible SQL injection attacks. If the string is composed using any user ...