![]() When the site starts up, Episerver compares the assembly version and the database version. To enable them, add attribute updateDatabaseSchema="true" to the amework element in configuration. Automatic schema upgradeīy default, automatic schema updates are disabled. Make sure you have a backup of the database before applying the update. All configuration transforms are now applied.ĭatabase schema transforms can be configured to run automatically as described in Automatic schema updates or applied manually (to avoid unintentional changes) when updating a package.Write Update-EPiConfig in the console and press Enter.Make sure "Default project" points to the website.Applying configuration transformsĬonfiguration transforms are applied automatically when updating a package so you only have to run this command if you for some reason want to re-apply configuration transforms or validate that all transforms were correctly applied: The database schema transformation files are also included as embedded resources in the assemblies to allow for automatic updates from versions 8.7.0 and 8.13.0. Since keeping track of these files and running them may be tedious work performed at regular intervals, a set of tools are provided as described below. Transformation files have to be executed in order. The transformation files are stored in the folder tools/epiupdates folder for each package (you can find all installed packages in the packages/ folder in the root folder of the Visual Studio solution). The transformation syntax for configuration files is XDT (XML Document Transform) and the transformation syntax for database schema are ordinary SQL files.īoth types of transformation files are cumulative and can be executed on any version of an installed product, each file has logic to make sure it only runs when required. When Episerver makes changes to the configuration schema or the database schema, those changes are incorporated into the NuGet package as transformation files. Similar packages are available for other products such as EPiServer.Commerce for the Commerce product. If you do not have any EPiServer NuGet packages installed, you can install the package EPiServer.CMS to get the latest version of all packages for Episerver CMS. When new updates are released, the affected packages are listed on Episerver World. All updates are cumulative meaning that the latest update always include previous updates. ![]() When installing a package, the dependent packages are also installed. The NuGet Package Manager displays the dependency information for each package. The EPiServer NuGet updates consist of a set of packages for different parts of the platform, with dependencies between them. From versions 7.6 and higher, changes to configuration and database schemas are managed as transformation files when updating. Refer to Installing Episerver updates for information on how to update Episerver through NuGet. This document describes how to manage configuration and database updates when updating Episerver using NuGet updates. Updating configuration and database schemas ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |