TitleUpgrading and Rolling back QuickApps – example 5.3 to 5.7 and then back to 5.3
- If customers have created custom skins for 5.3 and would like to continue to use those customer skins after upgrade, they will need to backup those skin files. This is provided as an option when they uninstall v5.3, which is part of the upgrade process (uninstall v5.3 and install version 5.7). There will be some customization work to make v5.3 custom skin work in v5.7 due to upgrade of the 3rd party control libraries.
- If the upgrade only involves Web Parts from 5.3 to 5.7, there is no content database migration involved, or SharePoint platform upgrade involved, then the upgrade is simply uninstall v5.3 and install v5.7. After installing v5.7, I would recommend launching Configuration Editor and check if there is any item listed to be fixed. The Configuration Editor performs web.config file backup automatically every time the tool makes change to the file.
- The upgrade essentially will retract and remove the v5.3 solution package from SharePoint and install v5.7 solution package to the SharePoint store. It will deploy the solution package to all Web front-end servers by installing files to GAC and SharePoint layouts folders. In addition, it will have help file, sample project and other misc. files installed to the Program Files/Quest Software folder. The upgrade will not touch or modify content database, so all Web Parts and pages configured will remain the same and will all work after the installation process is completed.