CODEWITHSUNDEEP
asp.net-mvc-3
knit
knit

Reputation: 23

static content pages in an MVC web application

I have just created my first MVC 3 project for a database search using EF db first, but the search is only a part of a big website most of the pages will just contain some text and images.

My question is basically about these pages which on the website would be .aspx, and the code behind would have nothing at all.

They use a master page and some user controls - my guess is that's the reason our front end person made them aspx not html.

I need to convert/include her pages into my project (I don't want to go back to stored procedures and listview after having used EF and Linq, plus I don't have time).

I know of one possible way: create a controller for each of the main menu items, then add ActionResult named for each of the submenu items returning View(), then create respective views. 

 public class LearnAboutStandardsController : Controller
    {

        public ActionResult Index()
        {
            return View();
        }
        public ActionResult ITSStandardsBackground()
        {
            return View();
        }
        public ActionResult ResearchInitiatives()
        {
            return View();
        }

So my static content pages will become Views.

It's working, I just want to do it for the rest of the pages and modify the links in the text of these pages.

Is there any other way to handle these pages?

There is no logic behind these pages.

I know this was not a perfect project for the MVC pattern with so much static content, but I had my reasons for it.

Upvotes: 0

Views: 2539

Answers (2)

John Prado
John Prado

Reputation: 804

I handle this with an "StaticContent" controller:

StaticContentController.cs

public class StaticContentController : Controller
{
    public ActionResult About()
    {
        return View();
    }

    public ActionResult Services()
    {
        return View();
    }

    public ActionResult Portfolio()
    {
        return View();
    }
}

Add the code below your route config to handle the static routes:

routes.MapRoute(
    "StaticContent",
    "{action}",
    new { controller = "StaticContent" },
    new { action = "About|Services|Portfolio" } // Add more here
);

You're set.

If you need more pages just add the action in the StaticController and adjust your StaticContent MapRoute.

Upvotes: 3

Eilon
Eilon

Reputation: 25704

Personally, I would have controllers with simple actions that just render views. That way if you do add more features later you're already set up. And if you want to add security or caching it's a lot easier and more consistent.

You can still use WebForms (with the new Friendly URLs feature if you want "pretty" URLs) for the "static" pages. Or you can use Web Pages with Razor and create CSHTML files for the static content.

Upvotes: 1

Related Questions