Deployment and Provisioning |
In a Migration Assessment this category evaluates migration options for customizations which are mainly used during the deployment and provisionig process of customizations.
Index
| Rule | Description | Type | Severity |
|---|---|---|---|
| SMA260401: Deploy TemplateFile as Module | TemplateFile is a file referenced in the package manifest manifest.xml. A module will allow for controlled deployment through features, without a module, the WSP will be blocked from deployment. | TemplateFile | CriticalWarning |
| SMA262101: Avoid deployment of Feature via Feature Framework | The Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | Feature | CriticalWarning |
| SMA265101: Avoid deployment of Fields via Feature Framework | Deploying fields through the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | Field | CriticalWarning |
| SMA265201: Avoid deployment of ContentTypes via Feature Framework | Deploying ContentTypes through the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | ContentType | CriticalWarning |
| SMA265401: Avoid deployment of List Instances via Feature Framework | Deploying List Instances through the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | ListInstance | CriticalWarning |
| SMA265501: Avoid deployment of List Definition via Feature Framework | Deploying List Definitions through the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | ListTemplate | CriticalWarning |
| SMA265601: Avoid deployment of ContentTypeBindingDefinition via Feature Framework | Deploying ContentTypeBindingDefinition through the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | ContentTypeBinding | CriticalWarning |
| SMA267001: Avoid deployment of Feature Staplings via Feature Framework | Using the Feature Stapling Feature of the Feature Framework creates dependencies on the provisioning XML files. Break this dependency to help future migrations, and updates by using the Remote Provisioning techniques from Microsoft. | TemplateAccociation | CriticalWarning |
| SMA267701: Consider different implementation of WebTemplate | There is no direct replacement for WebTemplate in the App Model. WebTemplate are used during creation of a site and provisions ListTemplates, ContentTypes etc. The alternative implementation focusses on a completely different approach for site provisiong. | WebTemplates | CriticalError |
| SMA267801: Consider different implementation of SiteDefinitions | There is no direct replacement for SiteDefinitions in the App Model. SiteDefinitions are used during creation of a site and provisions ListTemplates, ContentTypes etc. The alternative implementation focusses on a completely different approach for site provisiong. | SiteDefinitionManifestFileReference | CriticalError |
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 AB. 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.