Take the community feedback survey now.

smithsson68@gmail.com
Mar 31, 2011
  12047
(1 votes)

Upgrading CMS 6 R1 sites compiled against .NET 4.0

If your EPiServer CMS 6 R1 site is compiled against .NET 4.0 or is using components compiled against .NET 4.0 (Caste.Core for example), you will have problems upgrading your site to CMS 6 R2 using Deployment Center.

The problem is that the last step of the upgrade has to run in the context of the site. The way this is done is that Deployment Center starts a new AppDomain and loads the site into it as IIS would. However, by default, Deployment Center runs as a .NET 2.0 application and therefore cannot load a site with .NET 4.0 dependent assemblies.

The workaround is to run Deployment Center as a .NET 4.0 application by adding the following lines to its application configuration file:

<configuration>
   <startup>
      <supportedRuntime version="v4.0"/>
   </startup>
</configuration>

 

The Deployment Center configuration file can be found at the following path on the target machine:

{Program Files}\EPiServer\Shared\Install\EPiServerInstall.exe.config

Happy upgrading!

Mar 31, 2011

Comments

Fredrik Söderberg
Fredrik Söderberg May 3, 2011 05:04 PM

I couldn't start Deployment Center after putting
straight after the element. Putting it just before the last element solved the issue.

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Introducing the beta of Opti Graph Extensions add-on

Introducing Opti Graph Extensions: Enhanced Search Management for Optimizely CMS I am excited to announce the beta release of **Opti Graph...

Graham Carr | Sep 15, 2025

Content modeling for beginners

  Introduction Learning by Doing – Optimizely Build Series  is a YouTube series where I am building  a fictional  website called  TasteTrail , food...

Ratish | Sep 14, 2025 |

A day in the life of an Optimizely OMVP - Enhancing Search Relevance with Optimizely Graph: Synonyms and Pinned Results

When building search experiences for modern digital platforms, relevance is everything. Users expect search to understand their intent, even when...

Graham Carr | Sep 14, 2025

Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to...

Tomas Hensrud Gulla | Sep 14, 2025 |