Is this the correct pattern to return different views from an ASP.NET MVC controller?

Is this the correct pattern to return different views from an ASP.NET MVC controller?

I have an application that has an public 'end user' mode and a 'back office' mode. Both 'modes' pretty much share the same controller logic but the user interfaces for these different 'modes' are radically different.

Using the out of box default routing that you get when a project is created for the first time I have something like the following:

 Controllers\   HomeController.cs  Views   BackOffice     Index.aspx   Public     Index.aspx  Shared   BackOfficeSite.Master   PublicSite.Master 

In my HomeController.cs I have logic that looks like this:

public ActionResult Index() {   var devices = DeviceRepository.FindDevicesByCustomer(100);    if(IsBackOffice())    {      return View(@"~/Views/BackOffice/Index.aspx", devices);   }    return View(@"~/Views/Public/Index.aspx", devices); } 

Is this the correct way to be doing this or am I digging myself an anti-pattern hole?

I'm using ASP.NET MVC 2.

AJAX Call using jquery in mvc


Javascript not enabled
in your view folders you must place your BackOffice and Public in your Views/Home folder. deploying MVC 1.0 app with HTTPS
Views     Home       BackOffice         Index.aspx       Public         Index.aspx 
and your return View should look like this. Using System.ComponentModel.DisplayName with dynamic values?
return View("BackOffice/Index", devices);  return View("Public/Index", devices); 
the controller will always first look for the View inside the View Name folder of the controller. Strongly typed user control model binding not working in Asp.Net MVC 2.0If your Controller is HomeController, it will always look for the View at first in the Views/Home folder.. MVC2 Partial View throws/catches exceptions while resolving the path to the view
Send fax from ASP.NET MVC applicationHtml.ValidationMessageFor on Mono has strange results


I would say this if the data this both views need is the same, then it would be ok to use the same controller/route.. However, if they really are this radically different, then each view will likely need it's own set of data in which case, you may be digging yourself into a hole.. You might consider returning the result of ananother function instead of the view; any thing like this:.
return IsBackOffice()? receive BackOfficeView() : receive PublicView() ; 
This way you don't have a bunch of if/else in the same controller action..


I'd write a view engine to abstract this out. That way all your controller still has to did is:.
return View(); //or one of the overloads 

54 out of 100 based on 24 user ratings 184 reviews