This topic is only applicable to versions prior to CMS 12/Commerce 14, as these were based on ASP.NET Framework. For versions CMS 12 and Commerce 14 and higher, based on ASP.NET Core, see Install Optimizely (ASP.NET Core).
Optimizely continuously releases updates with new features and bug fixes using client-side NuGet packages.
Continuous release updates are cumulative to include previous updates. Optimizely supports all platform updates and strongly recommends that you keep ongoing projects up-to-date.
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 Optimizely Customized Commerce, it is important to ensure that you are running the same version of Optimizely Content Management System (CMS) and Optimizely Customized Commerce, both in the front-end and back-end applications.
- Add the Optimizely 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 Optimizely 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
NuGet package manager has to be version 2.8.50126.477 or higher to install Optimizely packages.
If you have no Optimizely NuGet packages installed, you can install the EPiServer.CMS package to get the latest version of all packages for Optimizely CMS. Similar packages are available for other parts of the Optimizely platform. Carefully read the package descriptions to ensure a smooth upgrade procedure.
See Commerce-specific updating steps before installing Optimizely Customized Commerce packages.
If you are using the Alloy sample site in CMS 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.
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 Optimizely 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.
To install a specific version, go to the Package Manager Console in Visual Studio and make sure it points to the Optimizely 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
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 Optimizely makes changes to the configuration schema or the database schema, those changes are incorporated into the NuGet package as transformation files.
If you are using Optimizely Customized Commerce, specific versions of CMS, and Live Monitor, there are additional steps needed to complete the updating. Depending on which version you currently are on, there may 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 Optimizely Customized Commerce and Optimizely Search & Navigation, but might also occur when updating CMS. The workaround is usually to update the packages one-by-one.
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).
Updated 4 months ago