0

I am developing an asp.net mvc website product that needs to allow customers to add their own content pages, outside of the project.

So the product will deliver a core set of pages (views) all using a master page. The clients can add their own web pages (.aspx) which I was hoping they could inherit from the MVC masterpage. Obviously there is no view context, so all of my html helpers, and Url.* calls fail.

What would be the best strategy to allow someone to add web pages into an mvc product, re-using as much of the structure as possible.

Improve this question
2
  • Can the client add an arbitrary number of pages? Or is there a set number of pages they are allowed to edit? Commented Jul 6, 2009 at 22:59
  • They can add as many as they want. The sitemap xml file will allow them to integrate these into the site seamlessly. Commented Jul 6, 2009 at 23:04

2 Answers 2

Reset to default
2

What you are describing is a Content Management System. There are a number of those available for MVC. One of them is N2. N2 is a lightweight CMS framework to help you build web sites that anyone can update:

http://n2cms.com/

Another one is Oxite. Oxite is a pure MVC CMS:

http://www.codeplex.com/oxite

These are open-source, so you can break them open and see how they did it.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

Scott Hanselman's blog post on how to mix together these technologies is required reading for anyone wanting to use ASP.NET MVC and classic ASP.NET together.

Plug-In Hybrids: ASP.NET WebForms and ASP.MVC and ASP.NET Dynamic Data Side By Side

Improve this answer

1 Comment

Yes, but this is more side-by-side not integration. I want to be able to use my MVC masterpage html from my web forms.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.