The “Thunderdome Principle” – All@H_403_4@ Controller methods take in one@H_403_4@ viewmodel object (or zero objects in@H_403_4@ some cases) and return a single@H_403_4@ viewmodel object (one object enters,@H_403_4@ one object leaves). The Controller@H_403_4@ classes will NEVER be directly exposed@H_403_4@ to anything related to HttpContext.@H_403_4@ Nothing makes me cry like seeing@H_403_4@ people trying to write tests that mock@H_403_4@ or stub that new IHttpContextWrapper@H_403_4@ interface. Likewise,Controller@H_403_4@ methods do not return ViewResult@H_403_4@ objects and are generally decoupled@H_403_4@ from all MVC infrastructure. We@H_403_4@ adopted this strategy very early on as@H_403_4@ a way to make Controller testing@H_403_4@ simpler mechanically. It’s definitely@H_403_4@ achieved that goal,but it’s also made@H_403_4@ the Controller code very streamlined@H_403_4@ and easy to read. We’ll explain how@H_403_4@ this works at KaizenConf.

他们的’一个viewmodel(或零)’方法有什么优势？