Expand Minimize


Checks files and artifacts for violations against naming conventions.


Rule Description Type Severity
SPC080101: Define Solution name as valid namespace To make it easier to identify the correct wsp solution in the solution store the name of the solution should be a valid namespace (e.g. 'Company.Project.Components.wsp'). Solution Warning
SPC080102: Files or Folders should contain the name of the parent solution Files or their folders should be named after the solution. This helps do make the file location unique to prevent overwriting of existing files and it is easier to see which WSP solution deployed the file. The rule is case sensitive. Solution Warning
SPC080103: Solution name should start with company name The solution name should start with company name to follow the rule 'CompanyName.ApplicationName.ComponentName.wsp'. Solution Warning
SPC080801: WebTemplate file in site definitions should start with 'WEBTEMP' The name of the WebTemplate files should start with 'WEBTEMP'. WebTempFile Warning
SPC082101: Feature name should start with solution name A feature name should be prefixed with the name of the parent solution. This helps to make the feature name unique and it is easier to see which WSP solution deployed the feature. The rule is case sensitive. Feature Warning
SPC082201: Declare FieldType in File 'fldtypes_[namespace].xml' The XML file which contains FieldTypes should follow the pattern 'fldtypes_[Namespace].xml'. [Namespace] represents the name of the WSP solution with replaced '.' with underscore. Reason: All FieldTypes are deployed to folder /SharePointRoot/Templates/XML and therefore must be stored in a file with a unique filename to avoid overriding existing FieldTypes from SharePoint or other custom solutions. FieldType Warning
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.