When you update a data structure on your local development machine, you can export the changes and then automatically import them on the next development environment from the continuous delivery process.
For example, if you update a dynamic module or add a custom field to a static module, you can export all changes. Sitefinity CMS saves them in a folder on the file system. After you transfer the folder to the next environment, upon initialization, Sitefinity CMS automatically applies all the changes.
PREREQUISITES: You have setup the Deployment mode.
When you export an updated data structure, Sitefinity CMS exports the following:
NOTE: Supported static modules are: News, Events, Lists, Blogs, and Libraries.
IMPORTANT: Associations between sites and providers are not exported.
After you make a change to a data structure that you want to transfer to the next environment, perform the following:
RESULT: When Sitefinity CMS starts on the next environment, it checks the content of folder ~\AppData\Sitefinity\Deployment. If any changes have been made to the files in the folder since the last Sitefinity CMS restart, Sitefinity CMS applies the changes uploaded in the folder. Sitefinity CMS checks, if there is difference in the names, sizes, or date modified of the files.
NOTE: The Deployment folder also includes any changes that you made to the modules that are coming from the add-on. For example, if you have a dynamic module that has been installed on your development environment with an add-on and afterwards, you add a custom field to this module, the custom field is transferred to the next environment via the Deployment folder, not in the AddOns folder. For more information, see Install and activate add-ons.
Navigate to Administration » Settings » Advanced » Packaging and (optionally) make the following setting to the packaging module:
IMPORTANT: The setting only applies to deleted modules but deleted types within a managed module are always deleted and the respective tables are dropped. Deleting types may result in data loss during development.
EXAMPLE: If you export the changes to data structures for each module, Sitefinity CMS creates a separate folder in the export folder. If you then transfer the export folder to the next environment, enable this setting on the next environment, and delete a module from the folder, Sitefinity CMS will delete the dynamic module from the system.
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important