SaaS CMS has officially launched! Learn more now.

Per Gunsarfs
Aug 17, 2012
  9729
(8 votes)

How to set up an empty CMS site with MVC support

I got a question regarding the MVC support in the EPiServer 7 Preview. How would you go about setting up an empty CMS site with MVC support?

If you install a site with the Alloy Tech templates, there is a zip module that adds MVC samples to the site. But what if you want to build MVC templates, but not install the Alloy Tech templates? I.e. have an empty site but with MVC tooling support. Here is what I did in order to get an empty MVC 4 project working with the EPiServer 7 Preview.

1. Install an empty CMS site using EPiServer Deployment Center.

2. Create a new ASP.NET MCP 4 Web Application, and choose the empty template.

CreateMVC

3. Copy the content of the folder containing the MVC project, i.e. the folder where the .csproj file resides. Skip the web.config files, global.ascx and global.ascx.cs. Paste the content in the site folder installed in step 1. I.e. the folder containing all the site files.

MvcFiles

4. In the parent folder of the MVC files there is a folder called packages. Copy that to the parent folder of the site files. This is needed in order to keep the references in the .csproj file intact.

Packages

5. Open the .csproj file and you’ll notice that the files global.ascx.cs, web.debug.config and web.release.config are missing. Just delete those references from the project.

6. Add any needed references to EPiServer assemblies. For a basic MVC template you will at least need EPiServer.dll, EPiServer.Data and EPiServer.BaseLibrary.

 

The project should now compile and now you can add your page types and templates. After doing so you will want to go to the UI and create a page. But since this an empty site it might not be obvious how to create the first page. Here is a short guide on how you could accomplish that.

1. Set pageStartId = 1 in episerver.config. The root page of the site is now your start page.

2. Go to edit, which can be found at http://{mysite}/{uipath}/modules/cms/home.

3. Create a new page under the root page. This will be your new start page.

4. Set pageStartId = 4(the id of the new page) in episerver.config.

You should now have a fully armed and operational CMS site.

Aug 17, 2012

Comments

Mari Jørgensen
Mari Jørgensen Sep 7, 2012 09:27 AM

Remember to add the following to web.config:




Ref: http://world.episerver.com/Modules/Forum/Pages/thread.aspx?id=60887&pageIndex=1#reply

Björn Sållarp
Björn Sållarp Oct 17, 2012 04:52 PM

Important note: You will need a global.ascx file in your MVC project that inherit from EPiServer.Global or url rewriting etc won't work.

Mattias Jöraas
Mattias Jöraas Oct 24, 2012 01:44 PM

When i create a MVC 4 site i get a "App_Start" folder too, containing 3 files (FilterConfig.cs, RouteConfig.cs, RegisterClientValidationExtensions.cs). Should these be hooked up somehow ?

Kazimierz Kuta
Kazimierz Kuta Oct 26, 2012 01:56 PM

In MVC 4 those classes are hoocked up in global asax by convention (look at Application_Start method). The reasoning behind this step was that Global.asax was getting way to big to maintain in some cases.

Andreas Ågren
Andreas Ågren Mar 22, 2013 11:43 AM

To create the first user that can be used to log in to the CMS, follow these steps:
1. In web.config, change /configuration/system.web/roleManager/defaultProvider to SqlServerRoleProvider and membership/@defaultProvider to SqlServerMembershipProvider.
2. Run the ASP.NET Configuration tool (can be found under the PROJECT menu).
3. Create a role that matches what's defined in web.configuration /configuration/location/system.web/authorization/allow/@roles, e.g. "Administrators".
4. Create a user and assign it to the newly created role.
5. You should now be able to log in to the CMS.

Please login to comment.
Latest blogs
Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024

Getting Started with Optimizely SaaS using Next.js Starter App & Configure local development - Part 2

This is part 2 of a proof-of-concept (POC) blog. In this post, I will guide you through the steps to configure your SaaS instance with your local...

Ragavendra | Jul 19, 2024 | Syndicated blog

Did Someone Say SaaS CMS?

Optimizely SaaS CMS quickstart guide

Daniel Isaacs | Jul 18, 2024 | Syndicated blog