Using similar Controllers in areas in Asp.Net Mvc

Question

I'm developing a sport based web site with Asp.Net Mvc 4.

The site is being developed to show just one sport data at a time.

The sports have similar datas in common but also they have different datas.

Site supports many sports that’s why, I do not want to use common controllers/views by seperating sports with if statements.

I tried this one:

I have created an area for each sport. I described the controllers in area which are related to that sport.

For example, in Route, name of the controller and area will be stated, firstly it will be searched in area, if it is not there, it will be searched in default(/Controllers).

Because the controllers share the same names, Mvc DefaultControllerfactory throws "Ambiguous Controller Name Exception". First I’m searching area, if it cannot be found then I’m searching in default by writing my own Controller factory. You can reach the project by the aid of the this link

In this case, my biggest deficiency is; without indicating namespace in route making the same thing in views. So it will search view in area, if it will not be found then it will search in default. Because the project is theme-supported, I use my own themable razor view engine, not default razor view engine. It can be reached by the aid of this link

base.AreaViewLocationFormats = new[]
{
  _themeService.Current.BasePath + "/Views/Areas/{2}/{1}/{0}.cshtml",
  _themeService.Current.BasePath + "/Views/{1}/{0}.cshtml",
  _themeService.Current.BasePath + "/Views/Shared/{0}.cshtml","~/Themes/Default/Views/{1}/{0}.cshtml"
};

I updated the object of AreaViewLocationFormats of RazorViewEngine like this but regardless of the fact that I state area in route, it searches ViewLocationFormats instead of AreaViewLocationFormats if I do not state namespace.

In this case, how should I separate sports?

Why don't you just have a table with different types of sports (e.g. "football", "tennis", etc.). Then your actions could take a parameter of the type of sport and return the appropriate view? — dav_i
– dav_i, Commented Jul 31, 2013 at 10:58
I tihnk the exception is thrown by the mvc DefaultControllerFactory when it tries to figure out which controller to instantiate, it may be worth having a look at multi-tenancy with something like autofac code.google.com/p/autofac/wiki/MultitenantIntegration — Daniel Powell
– Daniel Powell, Commented Jul 31, 2013 at 11:03
@DanielPowell, Because I wan't to use one Assembly for the Controllers, I need common(/Controllers). — onuralp
– onuralp, Commented Jul 31, 2013 at 11:15

ataravati · Accepted Answer · 2013-07-31 15:40:30Z

1

What I have done in a similar scenario is creating a base generic controller like this:

public abstract class BaseController<TModel> : Controller where TModel : class, new()
{
   // Controller Actions to be shared by all the controllers that inherit form this one...
}

And, then your controllers will be like this:

public class TennisController : BaseController<Tennis>
{
}

answered Jul 31, 2013 at 15:40

ataravati

9,1759 gold badges60 silver badges94 bronze badges

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

1 Comment

TheOptimusPrimus Over a year ago

Makes sense to me, base controller would have the fundamental properties for a "Sports" Controller.

Collectives™ on Stack Overflow

Using similar Controllers in areas in Asp.Net Mvc

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related