Sebastian Lundh
Dec 12, 2008
  12204
(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!

Please login to comment.
Latest blogs
Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |