SharePoint Customization Analysis Framework (SPCAF)

Code Quality

Managed CSOM

Best Practice

Consider implementing a pattern to avoid throttling with ClientContext.ExecuteQuery()

Consider verifying that the user has sufficient permissions when calling Web.Update().

Consider verifying that the user has sufficient permissions when calling Web.DeleteObject()

Consider verifying that the user has sufficient permissions when calling List.Update()

Consider verifying that the user has sufficient permissions when calling List.DeleteObject()

Consider verifying that the user has sufficient permissions when calling ListItem.Update()

Consider verifying that the user has sufficient permissions when calling ListItem.DeleteObject()

Consider verifying that the user has sufficient permissions when calling List.AddItem()

Consider verifying that the user has sufficient permissions when calling ListCollection.Add()

Consider verifying that the user has sufficient permissions when calling WebCollection.Add()

Untestable method found

Cyclomatic Complexity is used to check how testable a method is. This means any testing or Code Anlysis against this method is unreliable. 10+ requires refactoring, 15+ Poor code, 20+ High risk untestable, 50+ Unstable extremely high risk

CheckId	SPC059016
TypeName	UntestableDotNetMethod
Severity	CriticalWarning
Type	Assembly

Resolution

Refactor the method to reduce complexity

See also

Code Metrics - Cyclomatic Complexity

Message Suppression

To suppress this violation in managed code add the following attribute to the method which contains the instruction (available since SPCAF version v5.2). Learn more about SuppressMessage here.

// Important: Ensure to have #define CODE_ANALYSIS at the beginning of your .cs file
[SuppressMessage("SPCAF.Rules.ManagedCSOM.CSOMBestPracticesGroup", "SPC059016:UntestableDotNetMethod", Justification = "Provide reason for suppression here")]

SharePoint Customization Analysis Framework (SPCAF), 7.15.0.0

Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.