Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more


Sep 23, 2010
  11227
(0 votes)

EPiServer Community 4, Composer 4 and Mail 5 now supports ASP.NET 4.0

One month back we announced that EPiServer CMS 6 supports running on the ASP.NET 4 platform. Read more about that as well as some of the advantages with ASP.NET 4 in Allan Thræn’s article.

Today we are announcing that the following products also support ASP.NET 4.0:

To run each of these products on ASP.NET 4 you need to make the following configuration changes:

EPiServer Community 4

Make the following changes for EPiServer Community 4 in Web.config:

  • Remove sectionGroup System.Web.Extensions since it will conflict with same sectionGroup defined in machine.config:

    <sectionGroup name="system.web.extensions">... </sectionGroup>  
  • Remove the current HttpHandler for the IndexingService:
     
    <handlers>
    <clear/>
        …
    <add name="svc-Integrated" path="*.svc" verb="*" type="System.ServiceModel.Activation.HttpHandler, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" resourceType="Unspecified" preCondition="integratedMode"/>
        …
    </handlers>
     
    Add a new handler which reflects the new assembly that System.ServiceModel.Activation.HttpHandler resides in when using .NET 4.0:
     
    <add name="ServiceModel-4.0" path="*.svc" verb="*" type="System.ServiceModel.Activation.HttpHandler, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="managedHandler,runtimeVersionv4.0" /> 

EPiServer Composer 4

Make the following changes for EPiServer Composer 4 in Web.config:

  • Add the ScriptResourceHandler to make sure that all scripts are loaded correctly:
     
    <system.webServer>
    <handles>
    <add name="ScriptResourceHandler" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode"/>
    </handles>
    </system.webServer>
     
  • Remove the cross-site scripting protection in asp.net request validation:

    <system.web>
        <httpRuntime requestValidationMode="2.0"/>
    <pages validateRequest="false" />
    </system.web>
     

EPiServer Mail 5

Make the following changes for EPiServer Mail 5 in Web.config:

  • Remove sectionGroup System.Web.Extensions since it will conflict with same sectionGroup defined in machine.config:
     
    <sectionGroup name="system.web.extensions">... </sectionGroup> 
  • Change the redirect for assembly System.Web.Extensions from version 3.5.0.0 to 4.0.0.0.
     
  • Add in EPiServerMail\MailSources\EPiServerMailHTMLEditorMailSource.ascx:13:
      
    <asp:CustomValidator ClientValidationFunction="RadEditorNamespace.SaveAllEditors()//" runat="server" /> 
    before

    </asp:Panel> 
  • Add the attribute ClientIDMode set to AutoID for ComponentArt:MultiPage in EPiServerMail\MessagePopup.ascx:35:
     
    <ComponentArt:MultiPage id="multiPageTabs" runat="server" CssClass="multiPage" Width="99%" ClientIDMode="AutoID"> 

Related information

The following topics require member login:

More about EPiServer Community 4

More about EPiServer Composer 4

More about EPiServer Mail 5

Sep 23, 2010