Managed CSOM |
Intention
The quality rules for managed CSOM identify possible problems or coding errors in code using the client object model. The rules check the code and return violations as CriticalError, Error, CriticalWarning or Warning.
Rule Configuration
By default all recommended rules are checked. To disable rules or rule categories or to change the severity of a rule the SPCAF Settings Editor can be used.
Rule Severities
Each rule has a severity by default to classify the impact of a violation against the rule.
| Severity | Description |
|---|---|
| Error | Issues reported at Error level should not impact the solution deployment process or the stability of the SharePoint farm. But deployed solutions may not work as expected. Future upgrades of the solution maybe impossible or may most likely fail. WSPs or Apps with errors should only be deployed to SharePoint very carefully after the detected issues have been reviewed. |
| Warning | Issues reported at Warning level are generally concerned with doing things correctly to keep your code base stable, extensible, and maintainable. |
Category Index
| Category | Description |
|---|---|
| Correctness | Correctness rules check managed client side object model code. |
| Best Practices | Best Practice rules check managed client side object model code. |
| Performance | Performance rules check managed client side object model code. |
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.