Episerver is frequently updated through continuous releases. This topic describes how to update Episerver solutions using NuGet packages found in the Episerver NuGet feed.
Note: These instructions apply to Episerver versions 7 and higher.
Do the following to add the Episerver NuGet feed to Visual Studio, if you do not already have this:
Note: NuGet package manager has to be version 2.8.50126.477 or higher to install Episerver packages.
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 working on the Alloy template site in Episerver 7 or have a project deriving from that, see Updating a CMS project based on the Alloy template site before continuing; if you are running 7.5 or later, you can skip this step.
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.
If you are using Commerce, Relate, CMS Mirroring, CMO and Live Monitor, there are additional product-specific updating steps needed to complete the updating. Depending on which version you currently are on, there might be minor differences in the update procedure.
In some upgrade scenarios, you might experience problems with the dependency chains, due to issues in NuGet. This mostly affects Commerce and 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.
See the latest release information for a complete list of version-specific notifications.
To quickly get access to new features that are being developed, you can install Beta features, see Beta features for more information on how to work with these.
Last updated: Dec 01, 2016