Last updated: Dec 01 2016
Installing Episerver updates
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.
Upgrading an Episerver solution
- 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.
Adding the Episerver NuGet feed
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.
- Add Episerver as Name, and the package Source http://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.
Selecting and applying 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 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.
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
Updating configuration and database schemas
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 to 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, 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.
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 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.