ASP.NET MVC Core向导航页传值禁用菜单项及相关技术问题

Hey, let's break down your questions one by one with practical, pattern-aligned solutions for ASP.NET MVC Core:

问题1：从服务器端向导航页面传递值以禁用菜单项 #

There are two clean approaches I recommend for this, depending on how complex your menu logic is:

方法1：用ViewData/ViewBag传递状态（快速简单） #

Since your navigation is likely in a layout page (_Layout.cshtml), you can set state values either in individual controller actions or, better yet, in a base controller so all your controllers inherit the logic automatically.

First, create a base controller that runs logic before any action executes:

public class BaseController : Controller
{
    protected override void OnActionExecuting(ActionExecutingContext context)
    {
        // Replace this with your actual logic (e.g., user roles, subscription status)
        ViewBag.CanAccessProfile = User.Identity.IsAuthenticated && User.IsInRole("Registered");
        base.OnActionExecuting(context);
    }
}

Then make all your controllers inherit from this BaseController instead of the default Controller.

Now in your layout's Kendo Menu, check the ViewBag value to disable the item:

<div id="responsive-panel"> 
    @(Html.Kendo().Menu() 
        .Name("Menu") 
        .Items(items => { 
            items.Add() 
                .Text("Home") 
                .Action("Index", "Home"); 
            items.Add() 
                .Text("My Profile") 
                .Action("Index", "Profile")
                .Enabled(ViewBag.CanAccessProfile ?? false); // Use the server-side value to enable/disable
            items.Add() 
                .Text("Explore") 
                .Action("Index", "Explore"); 
        })
    )
</div>

方法2：用ViewComponent封装菜单（适合复杂逻辑） #

If your menu has lots of conditional logic (multiple roles, dynamic items, etc.), wrapping it in a ViewComponent keeps your layout clean and centralizes all menu logic in one place.

First, create the ViewComponent class:

public class MainMenuViewComponent : ViewComponent
{
    // Inject any services you need (e.g., user managers, permission services) here via constructor
    public IViewComponentResult Invoke()
    {
        // Build your menu items with server-side logic
        var menuItems = new List<MenuItemVm>
        {
            new MenuItemVm { Text = "Home", Action = "Index", Controller = "Home", IsEnabled = true },
            new MenuItemVm { Text = "My Profile", Action = "Index", Controller = "Profile", IsEnabled = User.IsInRole("Registered") },
            new MenuItemVm { Text = "Explore", Action = "Index", Controller = "Explore", IsEnabled = true }
        };
        return View(menuItems);
    }
}

// Simple view model to hold menu item data
public class MenuItemVm
{
    public string Text { get; set; }
    public string Action { get; set; }
    public string Controller { get; set; }
    public bool IsEnabled { get; set; }
}

Next, create the ViewComponent's view at Views/Shared/Components/MainMenu/Default.cshtml:

@model List<MenuItemVm>

<div id="responsive-panel">
    @(Html.Kendo().Menu()
        .Name("Menu")
        .Items(items => {
            foreach (var item in Model)
            {
                items.Add()
                    .Text(item.Text)
                    .Action(item.Action, item.Controller)
                    .Enabled(item.IsEnabled);
            }
        })
    )
</div>

Finally, replace your menu code in the layout with a call to the ViewComponent:

@await Component.InvokeAsync("MainMenu")

问题2：导航页无对应Controller，如何设置值并通过Razor调用服务器端方法 #

Great question—layouts don't have their own controllers, but they're rendered as part of every request, so you have a few solid options:

Option 1: Use a base controller or global filter #

As I showed in the first method, a base controller's OnActionExecuting method runs for every request, so you can set ViewBag/ViewData values there that the layout can access. This ensures the value is set before the layout renders.

Option 2: Call server-side methods directly in Razor #

You absolutely can call server-side code directly in Razor (including layouts):

• Static helper methods: If you have a static class with logic, call it directly:

  .Enabled(MenuHelpers.CanAccessProfile(User))
  

• Injected services: If you need access to a registered service (like a permission service), use the @inject directive at the top of your layout:

  @inject IPermissionService PermissionService
  
  <!-- Then in your menu code: -->
  .Enabled(PermissionService.CanAccessProfile(User))
  

This approach avoids passing values through ViewBag and keeps your layout logic directly tied to the service that handles permissions.

内容的提问来源于stack exchange，提问作者punkouter