Review declarative security for {0} and its callers for potential vulnerabilities. This method is accessible from outside its assembly, and might therefore provide a way to circumvent security protection. Consider removing SuppressUnmanagedCodeSecurity from the method or make it private and wrap it with a public method that demands a permission appropriate to the P/Invoke functionality and security risk.
Reuse Properties If a property is already applied style application modifies the applied rule instead of the target rule. ...
Reverting this activity will lose any changes you've made, and get the latest details from the server. Are you sure you want ...
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 ...