EPiServer Pie with freshly cut MVC

by: Allan Thræn

Or how to integrate ASP.NET MVC into an existing WebForms Web Application Project.


After having studied Scott Guthrie's excellent posts on ASP.NET MVC and attended a pretty good Tech Talk at Microsoft yesterday I decided the time was right to start playing around with integrating MVC code in the same project as a typical EPiServer CMS 5.1 web application. It turned out to be fairly easy - didn't take more than 1 hour of evening coding ( there wasn't anything good on the telly anyway) - so here is a short recipe for all of you out there.

If you want to read more about ASP.NET MVC before you start, read here. To many it might present quite a paradigm change in web development (and I've personally not yet totally decided whether I think it's an improvement or not) so I imagine we'll be seeing a lot of cases where it's mixed into ordinary web projects, where it's strengths are best utilized. That's why it made sense to me to mix it with a standard EPiServer project.



  • Working EPiServer CMS 5.1 web project with source and project files
  • VS 2008
  • ASP.NET 3.5 Extensions Preview (this recipe uses the December Preview - but if you're trying this after the MIX08 preview, drop a comment and let me know how it worked out!)


Step-by-step guide to baking your pie :-)

  1. Open your EPiServer CMS project in VS 2008 and use the wizard to upgrade it. When it's upgraded, go to Project properties and set the target framework to ".NET Framework 3.5". Save and run in visual studio web server to make sure it works as expected.
  2. In the project references, there is most likely a reference to System.Web.Extensions and System.Web.Wextensions.Design. Remove them, then add them again - but make sure you add the version - not the that you had before. This is actually the tricky part. Even though both assemblies are in the GAC I wasn't able to persuade VS to get the right version. If you also have problems, then copy the assembly out of the GAC and add it as a reference by browsing to the dll. It can be copied out of the GAC like this:
    copy "C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions\" "c:\myproject\"
  3. Now it's time to update your web.config. First I changed the assembly binding to look like this:
  4.     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
            <bindingRedirect oldVersion="" newVersion=""/>
            <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
            <bindingRedirect oldVersion="" newVersion=""/>
  5. Then it was time to setup the UrlRouting module that's a vital part of MVC. I found that it can coexist quite peacefully with EPiServer's Friendly Url rewriting - just add the module in the top of the http-modules list in web.config:
  6. <add name="UrlRoutingModule" 
    System.Web.Extensions, Version=, Culture=neutral,
  7. So far, so good. Now put it in the oven at 200 degrees and let it bake for 30 min and your EPiServer pie will be done. However we still need to sprinkle some MVC on top until now we've only prepared the platform - but we still need to make our fancy-smancy-state-of-the-art-super-microsoft-will-love-us-and-it-will-taste-great MVC code...And the first place I'll start is by setting up the URL Routing in Global.asax.
    First, make sure Global.asax.cs is included in your project and that Global.asax inherits from you code - that in turn inherits from EPiServer.Global.
    Then, I put in the following code to ensure that everything in the url path /mvc/ is handled by the MVC Url Routing:
  8. protected void Application_Start(Object sender, EventArgs e)
      RouteTable.Routes.Add(new Route
        Url = "mvc/[controller]/[action]/[id]",
        Defaults = new { action = "Index", id = (int?)null },
        RouteHandler = typeof(MvcRouteHandler)
  9. Now, it's really just left for us to make some MVC functionality. As an example I decided to make two MVC Actions. One will get a list of all pages that are visible in menus and show it, the other will list all properties for a given page. That way we'll see some interaction with EPiServer as well. I made a "Controllers" folder in my project, along with a "Views" folder that had a subfolder "Page" (since I decided that my controller would be a PageController). Then I used the visual studio templates to generate a PageController, and two views. The data model for what I want to achieve already exists in EPiServer (PageData) so I saw no reason to make a new one. After a while my project looked like this:
  10. In the PageController, I made two actions - one "Index" would perform a search for pages visible in menus and send them to a view, the other would show the properties of a page. Here's the code:
  11.     public class PageController : Controller
            public void Index()
                PropertyCriteriaCollection pcc=new PropertyCriteriaCollection();
                pcc.Add(new PropertyCriteria() { 
                    Required = true, 
                    Condition = CompareCondition.Equal, 
                    Name = "PageVisibleInMenu",Value="True", 
                    Type=PropertyDataType.Boolean });
                PageDataCollection pdc = DataFactory.Instance.FindPagesWithCriteria(
                    PageReference.RootPage, pcc);
            public void ShowPageData(int id)
                PageData p = DataFactory.Instance.GetPage(new PageReference(id));
                RenderView("PageDataView", p);
  12. Then it became time to look at the views. I modified the code-behind in each view to make it inherit from a generic ViewPage with a datatype corresponding to the data I was sending to it - like ViewPage<PageData>. From there on it was just a matter of spraying a few simple lines of mixed html and code in the view - and voila!
  13.    <ul>
        <% foreach (EPiServer.Core.PageData p in ViewData)
           { %>
        <li><%= Html.ActionLink(p.PageName,new {controller="Page", action="ShowPageData", id=p.PageLink.ID}) %></li>
        <% } %>
  14. Follow the same approach and you'll easily be able to display the properties as well. Here's the final result:

mvc2 mvc3



21 February 2008


  1. This is very cool stuff. Nice to see that the MVC framework so seamlessly plugs into an existing architecthure. I'd like to see this done with a fallback to standard ASP.NET pages, maybe I'll try it out soom. Great post Allan!
  2. I appreciate your effort to share this with the rest of us! I think of myself as a .Net developer currently working with EPiServer and sometimes I feel like I'm falling behind in technology. This time your effort proved me wrong!
  3. Awesome, Allan! I've been really interested in using MVC with EPiServer, but I haven't gotten around to any "recreational programming" on it yet! So, thanks for the intro!
  4. Very cool Allan! Though isn't there a "architectural conflict" in the way EPiServer uses FURLs? I tried this and while using it on templates not beeing EPi pagetypes works perfect, I got stucked on how I would do this if the pages where actuall EPiServer-pagetypes. For example Im thinking; How would you use the edit mode when the MVC routing is turned on, I tried it but since MVC routing has decided, for example, there are no /template/pages/something.aspx links anymore - .NET spits standard "The resource cannot be found" errors. Any ideas on this?
  5. Addition to last comment: The URL /template/pages/something.aspx was a mistake, I ment to write http://localhost/en/something/ (if localization is english and page shortcut name in "something". I am tempted to write a urlrewrite module based on the EPiServer UrlRewrite module so that is uses the MVC routing instead, do you see that there would be any mayor problems with this idea? Would anything more need to be rewritten in order to fully integrate MVC routing with EPiServer?
  6. Come on, Allan. Answer Mattias' question from 13 July 2008.
  7. Sorry for the late answer. Apperently the "email-when-someone-comments" functionality has stopped working here - I just stumpled upon these by accident. I agree with you Mattias, that in order to fully replace webforms with MVC in EPiServer, you'd need to make a new rewrite module - or perhaps totally replace it with url-routing. I'm not sure exactly what would be needed to do this. What I wanted to show in this example was not that you could replace webforms with mvc in EPiServer CMS, but rather that both development techniques can work together. To some degree it's a matter of taste, but I still prefer to do 'regular' web development using webforms - but sometimes switch over to MVC when making functionality. Since this post was written, the UrlRouting engine in MVC has become part of the standard .NET framework (3.5 SP1) and in later posts I've shown how to use it together with webforms. Check out WikiX for a lot of codesamples on how this can work together.
  8. AS a girl, Wedding Apparel I like New Style Wedding Dresses the dress A-line Wedding Dresses very Ball Gown Wedding Dresses much. Empire Wedding Dresses I think Princess Wedding Dresses when the Sheath Wedding Dresses girl dress Column Wedding Dresses different dresses, Mermaid Wedding Dresses it can reflect different Trumpet Wedding Dresses feeling. Plus Size Wedding Dresses I have Celebrity Wedding Dresses buy one Maternity Wedding Dresses on the line. Little White Wedding Dresses I received Wedding Dresses UK it before Wedding Dresses with Color few days. Wedding Dresses with Sleeves I am Free Shipping Wedding Dresses satisfied Bridesmaid Dresses with it. Bridesmaids Dresses I hope that everyone likes it.
Post a comment    
User verification Image for user verification  
Allan Thræn

About me

I am a product manager @ EPiServer, with a passion for the more geeky side of things. My technical interests are typically focused around user problems, user experience,  search, information management, artificial intelligence and  personalization

On top of this blog I have the blog Allan On Technology and I often crosspost.

DISCLAIMER: Unless otherwise stated in the posts, this blog expresses my personal opinions, experiments and views, not necessarilly the views of EPiServer AB.

  page views this week.





Tag cloud

EPiTrace logger