SPC052101: Do not activate or deactivate Features via API |
Do not activate or deactivate Features in code via API. Consider using PowerShell or Feature Stapling.
| CheckId | SPC052101 |
|---|---|
| TypeName | DoNotActivateFeaturesViaAPI |
| Severity | CriticalWarning |
| Type | Assembly |
Remove calls to SPFeatureCollection.Add() and SPFeatureCollection.Remove() to activate or deactivate Features. Use PowerShell or Feature Stapling instead.
Bad Practice
// code activates a feature in current web
SPWeb currentWeb = SPContext.Current.Web;
currentWeb.Features.Add(new Guid("{75bb640f-a94e-4893-819c-6ef5f14e1984}"));
SPWeb currentWeb = SPContext.Current.Web;
currentWeb.Features.Add(new Guid("{75bb640f-a94e-4893-819c-6ef5f14e1984}"));
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.BestPracticesGroup", "SPC052101:DoNotActivateFeaturesViaAPI", Justification = "Provide reason for suppression here")]
[SuppressMessage("SPCAF.Rules.BestPracticesGroup", "SPC052101:DoNotActivateFeaturesViaAPI", Justification = "Provide reason for suppression here")]
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.