CODEWITHSUNDEEP
c#asp.net-mvcasp.net-mvc-3
Stachu
Stachu

Reputation: 5857

Need to access a variable from all Views

On the site I'm working on, there are users with different permissions on the site.

Given the schedule ID and employee ID that we're currently looking at, we can get their role-specific permissions.

Right now, our BaseModel has a property that properly accesses the DB and grabs this info. For all views that pass a model to the view, everything runs fine.

The problem lies in Controller Methods where no model is passed. In a few views, all they're supplied is a few ViewBag entries, and work fine.

However, I /need/ the CurrentPermissions property in those pages nonetheless, for the layout. Whether or not the permissions have one boolean value set true/false, something may/may not be displayed/populated.

So, my option seem to be:

How can I go about pushing this CurrentPermissions object (generated from a call to my TransactionManager) to every view (specifically, the Layouts!)

Upvotes: 1

Views: 375

Answers (2)

Romias
Romias

Reputation: 14133

Your approach is what we use in out projects... and we use this approach to systematically remove the use of ViewBag changing it to ViewModels.

Other approach we have used (for UserPreferences in my case) is adding an ActionFilter that ends including the preference in the ViewBag. You decorate the actions needing it with [IncludePreferences] in my case (that is the name of my filter attribute.

EDIT ActionFilter:

public class IncludePreferencesAttribute : ActionFilterAttribute
{
       public override void OnActionExecuting(ActionExecutingContext filterContext)
       {
              var controller = filterContext.Controller as BaseController;

              // IController is not necessarily a Controller
              if (controller != null)
              {
                     //I have my preferences in the BaseController
                     //and cached but here you can query the DB
                     controller.ViewBag.MyPreferences = controller.TenantPreferences;
              }
       }
}

In you action you decorate it using [IncludePreferences]

Upvotes: 1

Stachu
Stachu

Reputation: 5857

As a temporary solution, I'm doing the following at the top of my Layout:

@{ OurModel.SupervisorRestriction CurrentSupervisorRestrictions = ViewBag.CurrentSupervisorRestrictions ?? Model.CurrentSupervisorRestrictions; }

This way, if we're passing in an object then it works just fine. Otherwise, I'll directly pass in a ViewBag.CurrentSupervisorRestrictions from the controller. There are only a few cases, so it's not that bad.

Better suggestions would be great, though.

Upvotes: 0

Related Questions