Try our conversational search powered by Generative AI!

AI OnAI Off

Product-specific updating steps

This topic describes additional steps required to complete the updating of Episerver solutions using NuGet.

Note: Relate, Community, CMO, and mirroring are no longer supported.

CMS

Sites installed using the legacy tool EPiServer Deployment Center has binding redirects in web.config for assemblies not owned by Episerver. These assemblies are now managed by NuGet which might cause conflicts since NuGet might decide no redirect is required.

Example error during startup of the site: Could not load file or assembly 'Castle.Windsor, Version=3.2.0.0

In this example remove the following sections (or change the version number to the version of the installed NuGet package, see packages.config for version numbers):

<dependentAssembly>
<assemblyIdentity name="Castle.Core" publicKeyToken="407dd0808d44fbdc" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.3.0.0" newVersion="3.3.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Castle.Windsor" publicKeyToken="407dd0808d44fbdc" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.65535.65535.65535" newVersion="3.2.0.0" />
</dependentAssembly>

 

Commerce

Refer to Commerce-specific updating steps for information how to update Episerver Commerce solutions.

Relate [Legacy]

Both the CMS and Community have their own blog implementations. When applying the update to a Relate project, it automatically gets a reference to EPiServer.Blog from the CMS package. This blog system conflict will likely generate a build error.

error CS0118: 'EPiServer.Blog' is a 'namespace' but is used like a 'type'

The easiest way to circumvent this is to manually delete the EPiServer.Blog reference. Also remove any assembly redirect for EPiServer.Blog in web.config.

Community [Legacy]

If for instance you want to add community support to a project, adding just the Community and Common Framework components will not work since that will not add necessary configuration and database changes to your project.

Projects with mirroring [Legacy]

If you have mirroring configured in your project, you need to manually update the binaries in the associated mirroring service application to match the assemblies in the project bin folder. You also need to update mirroring service configuration to point it to the new versions of the assemblies. Set the bindingRedirect element according to this:

<bindingRedirect oldVersion="5.2.375.0-7.0.586.16" newVersion="7.0.586.16" />

CMO [Legacy] and Live Monitor

If you are applying updates for CMO and LiveMonitor components you need to do some additional changes to your project afterwards.

Installing Episerver modules for an updated project

This section applies to Episerver modules such as CMO or Live Monitor. The updated assemblies have new version numbers, and as a consequence Deployment Center will not be able to list your site when selecting target site for module installation.

Install modules on a updateed project as follows:

  1. Open Deployment Center.
  2. Go to the All actions tab.
  3. Expand EPiServer CMS > Version 7.X.XXX.X (your version) > Modules.
  4. Select the module to install.
  5. In the select site wizard, select Show All Sites.
  6. Select your updated site and complete the installation.