c# 如何实现mvc模式

ASP.NET Core MVC 是官方推荐的、开箱即用的 MVC 实现，不是靠手写三个类模拟出来的“伪 MVC”。直接用框架，别自己造轮子。

为什么不用手动实现 Controller/Model/View 分层

手写

Controller

IView

ViewEngine

MvcOptions

IActionResult

ViewResult

Controller

ControllerBase

IActionResult

Views/{ControllerName}/{ActionName}.cshtml

@model

最简可行的 MVC 三件套写法

以一个显示用户列表的场景为例，不引入数据库或服务层，聚焦结构本身：

@* Views/Home/Index.cshtml *@
@model List<User>
<p><h2>用户列表</h2>
<ul>
@foreach (var user in Model)
{
<li>@user.Name (@user.Email)</li>
}
</ul>

// Controllers/HomeController.cs
public class HomeController : Controller
{
    public IActionResult Index()
    {
        var users = new List<User>
        {
            new User { Name = "张三", Email = "zhang@example.com" },
            new User { Name = "李四", Email = "li@example.com" }
        };
        return View(users); // 自动查找 Views/Home/Index.cshtml
    }
}

// Models/User.cs
public class User
{
    public string Name { get; set; }
    public string Email { get; set; }
}

常见踩坑点：View 和 Controller 不匹配

错误现象：

The view 'Index' was not found.

InvalidOperationException: The model item passed into the ViewDataDictionary is of type 'System.Collections.Generic.List`1[MyApp.Models.User]', but this ViewDataDictionary instance requires a model item of type 'MyApp.Models.User'.

return View(users)

List<user></user>

@model User

@model List<user></user>

Index.cshtm

Views/Shared/Index.cshtml

[ViewLocationFormats](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.razorviewengineoptions.viewlocationformats)

public IActionResult Index()

public void Index()

需要自定义行为时，优先扩展而非重写

比如想统一处理未授权请求，不要重写整个

Controller

// Filters/RequireAuthFilter.cs
public class RequireAuthFilter : IAuthorizationFilter
{
    public void OnAuthorization(AuthorizationFilterContext context)
    {
        if (!context.HttpContext.User.Identity.IsAuthenticated)
        {
            context.Result = new RedirectToActionResult("Login", "Account", null);
        }
    }
}

然后在控制器上加

[TypeFilter<requireauthfilter>]</requireauthfilter>

services.AddControllersWithViews(options => options.Filters.Add<requireauthfilter>());</requireauthfilter>

真正难的从来不是“怎么分三层”，而是路由怎么配、模型绑定怎么调、ViewComponent 怎么复用、TagHelper 怎么写——这些才是日常高频问题。MVC 结构只是骨架，血肉全在配置和约定里。