ASP.NET MVC - 查看模型模式(ASP.NET MVC - View Model pattern)

 我现在只使用MVC框架（ASP.NET MVC2 / 3 / Razor）几个月了，我真的很享受它，但是我很难找到View Models的标准。 在我的项目中，我有一个Models文件夹（包含我的数据模型 - Linq DBML，Repository [ies]，扩展方法）和Models / ViewModels文件夹。 我的视图模型通常是可重用的类，通常只包含LINQ对象的简单get / set属性或我需要为特定视图访问的对象集合。 
 
 现在我遇到的问题是弄清楚何时创建一个视图模型。 我的目标是尽可能经常使用LINQ对象作为视图模型，尤其是当它是一个Edit动作时。 我的问题是，如果我有其他数据，我可能只想用于显示目的？ 我不喜欢使用ViewData / ViewBag集合，因为访问这些集合的成员需要了解集合项的密钥（设计人员/前端人员不容易“猜测”）。 我也不喜欢为每个View创建一个ViewModel的想法，因为它似乎是不必要的混乱代码。 
 
 例如，假设我有一个Employee的数据模型，我想显示一些与该员工无关的信息 - 例如，站点统计信息，动态菜单以及您可能想到的可能来自数据库的任何其他信息。 我应该通过什么模型/ Employee / Edit操作？ 带有一堆ViewData []的Employee对象，还是自定义的EmployeeView？ 
 
 有金标准吗？ 我错过了什么？ 你在做什么不同我应该研究一下？ 提前致谢！ 

I have only been working with the MVC framework (ASP.NET MVC2/3/Razor) for a few months now and I am really enjoying it, however I am having a hard time figuring out a standard for View Models. In my projects, I have a Models folder (Contains my data models - Linq DBML, Repository[ies], Extension methods) and a Models/ViewModels folder. My view models are usually reusable classes which usually just contain simple get/set properties for the LINQ objects or collections of objects I need to access for a particular view.
 
Now the problem I am having is figuring out when to create a view model. My goal is to use the LINQ object as the view model as often as possible, especially when it is an Edit action. My problem is what if I have other bits of data that I might want to use for display purposes only? I don't like to use the ViewData/ViewBag collections, as accessing members of these requires knowledge of the collection item's key (not easy for a designer/front-end guy to "guess"). I also don't like the idea of creating a ViewModel for each View, as it seems like unnecessarily messy code. 
 
For example, imagine I have a data model for an Employee, and I want to display some information unrelated to that employee - say, site statistics, dynamic menus, and whatever else you can think of that might come from the database. What model should I pass the /Employee/Edit action? The Employee object with a bunch of ViewData[] for the rest, or a custom EmployeeView?
 
Is there a gold standard? What am I missing? What are you doing different that I should look into? Thanks in advance!

原文：https://stackoverflow.com/questions/6077913