Sebastian Lundh
Dec 12, 2008
visibility 12273
star star star star star
(0 votes)

EPiServer Mail 4.3 to work with R2

While the development team is working on installer packages for EPiServer Community and EPiServer Mail for the new EPiServer Installation manager there are some workarounds that can be performed to run EPiServer Mail on R2.

Other than the normal instructions at:
http://world.episerver.com/en/Documentation/Items/Installation-Instructions/Create/Installation-Instructions---Create/

There’s a problem with the EPiServer Mail installer and that in R2 the UI folder is moved to: C:\Program Files\EPiServer\CMS\5.2.375.7\Application
<add virtualPath="~/SUI/" physicalPath="C:\Program Files\EPiServer\CMS\5.2.375.7\application\UI" name="UI" type="EPiServer.Web.Hosting.VirtualPathNonUnifiedProvider,EPiServer" />

You can copy that  folder back to your sites root and name it correctly and remove the Virtual path entry for the UI folder. If you want, after installation you can just copy the UI/Mail folder to the UI folder located in program files and add the virtual path again.

Also you will have to remove all entries to System.Web.Extensions 1.0 if you have that installed already, like:
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

<add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

Then add assembly redirect for 1.0 to 3.5:

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>

Edit:
You also need to make sure that you use full path to UI folder in site settings:
uiUrl="http://site/SUI/"

Dec 12, 2008

Comments

Per Hemmingson
Per Hemmingson Sep 21, 2010 10:32 AM

Good post Seb!

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |