Upgrade Sitefinity via Merge
At the link above in step 3, bullet point 2 it states the following:
Merge your live website with the upgraded one.
If you want to merge the locally upgraded website with the production website without replacing the database, perform the following:
Package the upgraded website without the configuration files from ~/App_Data/Sitefinity/Configuration. Do not include the locally upgraded database.
Are all files to not be included? I would think that the dataconfig.config file would be needed since that includes the connection to the DB. Anyone perform an upgrade via a merge that could answer this?
Hi,
Are all files to not be included?
Include only the files for the site without the configuration files for Sitefintiy located at ~/App_Data/Sitefinity/Configuration. This is because a Sitefinity upgrade replaces the assemblies that the site uses and makes updates to web.config. With updated assemblies and web.config once the site is started the upgrade process executes and updates the database and configuration files in ~/App_Data/Sitefinity/Configuration and this is the reason configuration files must be from the non-upgraded version of the site.
DataConfig.config and also all other configs remain the same since it is a production site which is running and gets merged with an upgraded copy of the site files that contain new assemblies.
Regards,
Stanislav Velikov
Telerik
I have the project setup to store the configurations in the database, so when that happens the files become read-only. With that said, how is the update process different when site is set to store configuration in the DB? I have been unable to complete a successful merge with the upgraded solution.
Hello,
When the configuration files are in the database then the configurations that are stored in the file system are not updated or affected by the upgrade since those files in the file system are a fallback version(read-only) of the configurations in the database. There will not be no change in the upgrade process when the configs are stored in the database.
Is it possible to move the upgraded site files from the development environment to live and connect then to the non-upgraded site database (creating a backup first) which will upgrade the database and the configuration files in it.
Regards,
Stanislav Velikov
Telerik