Views: 7879
Number of votes: 8
Average rating:

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

Mari Jørgensen
(By Mari Jørgensen, 9/7/2012 11:27:18 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
(By Björn Sållarp, 10/17/2012 6:52:12 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
(By Mattias Jöraas, 10/24/2012 3:44:37 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
(By Kazimierz Kuta, 10/26/2012 3:56:34 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
(By Andreas Ågren, 3/22/2013 12:43:28 PM)

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.