Installing Episerver updates
Episerver continuously releases updates with new features and bug fixes using client-side NuGet packages. This topic describes how to update an Episerver solution through NuGet packages from the Episerver NuGet feed.
Note: These instructions apply to Episerver versions 7 and higher.
About the updates
Continuous release updates are cumulative to include previous updates. Episerver supports all platform updates and strongly recommends that you keep ongoing projects up-to-date.
Note: A product release may contain multiple NuGet packages with inter-dependencies. When a release is built, other dependent packages may also be bumped to new versions, although they contain no publicly visible changes. This is done to avoid dependency errors. When you upgrade, NuGet alerts you to upgrade related packages to the required versions. For Commerce, it is important to ensure that you are running the same version of CMS and Commerce, both in the front-end and back-end applications.
- Add the Episerver NuGet feed to the NuGet package manager in Visual Studio (if not done).
- Select and apply packages to install. Upgrades are cumulative: the latest includes previous updates.
- Update configuration and database schemas. If upgrading to a new major version, see breaking changes information for related fixes.
- Deploy the updates to your different environments.
Do the following to add the Episerver NuGet feed to Visual Studio, if you do not already have this:
- In Visual Studio, select Tools > NuGet Package Manager > Package Manager Settings.
- Select Package Manager > Package Sources.
- Click the green + sign to add a new package source.
- Add Episerver as Name, and the package Source https://nuget.episerver.com/feed/packages.svc/.
- Click OK.
Note: NuGet package manager has to be version 2.8.50126.477 or higher to install Episerver packages.
Select packages to update to
If you have no Episerver NuGet packages installed, you can install the EPiServer.CMS package to get the latest version of all packages for Episerver CMS. Similar packages are available for other parts of the Episerver platform. Carefully read the package descriptions to ensure a smooth upgrade procedure.
Note: See Commerce-specific updating steps before installing Commerce packages.
Note: If you are using the Alloy sample site in Episerver 7 or have a project deriving from that, see Updating a CMS project based on the Alloy sample site before continuing; if you are running 7.5 or later, you can skip this step.
Applying an update
- Open the solution file in Visual Studio and make sure the solution file is saved (required to make the NuGet tools available).
- In the Solution Explorer, right-click on References for the project, and select Manage NuGet Packages.
- Select Updates for the Episerver package source to locate available updates for your solution, and click Update for the desired packages.
- When the installation/update is completed, rebuild the solution.
- See product-specific updating steps for steps required to finalize the update.
Installing a specific version
To install a specific version, go to the Package Manager Console in Visual Studio and make sure it points to the Episerver NuGet feed. Install or update the packages of your solution as shown in the following examples:
Install-package EPiServer.CMS -Version 9.0.0
Update-Package EPiServer.CMS -Version 9.0.0
Note: The database user connecting to SQL Server must be granted access to perform schema changes on the database. Members of the db_owner fixed database role can perform all configuration and maintenance activities on the database, including schema changes.
- From version 8.7: By default, the cmdlet Update-EPiDatabase is used to manually update the database schema. From version 8.7 you can configure the site to automatically apply updates to the SQL schema during site initialization.
- From version 7.6: When Episerver makes changes to the configuration schema or the database schema, those changes are incorporated into the NuGet package as transformation files. See Updating configuration and database schemas for information about manually deploying changes to configuration and database transforms when needed.
Product-specific updating steps
If you are using Commerce, specific versions of CMS, and Live Monitor, there are additional product-specific updating steps needed to complete the updating. Depending on which version you currently are on, there may be minor differences in the update procedure.
Issues with NuGet
In some upgrade scenarios, you might experience problems with the dependency chains, due to issues in NuGet. This mostly affects Commerce and Search & Navigation (formerly Find), but might also occur when updating CMS. The workaround is usually to update the packages one-by-one. See Issues with NuGet package updates.
To get an early start and access new features that are being developed, you can join a Beta program and be part of a CTP (Community Test Preview), see Episerver service and product lifecycles.
Last updated: Jun 11, 2020