blocks|key|2161921|text|This+site有一个很好的图表来解释这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2161922|基本上你有3个组件：|2161923|1)+模型-应用程序的数据模型。这是非常标准的，和任何MVP或MVC应用程序一样。|style|BOLD|2161924|2)+XAML视图--定义你的应用的视图/布局的。|2161925|3)+视图模型--因为WPF要求视图以某种方式附加到事物上(比如要求集合实现INotifyCollectionChanged之类的东西)，所以通常需要您稍微修改一下数据，以使其以适合视图显示的形式显示。这就是视图模型编码的位置。它将数据打包到视图模型中，以便视图可以轻松显示。这是您的视图XAML将绑定到的内容。它必须响应来自模型层的事件并自我更新。|2161926|(然后您的控制器挂在一边的某处-理想情况下使用WPF命令-并对模型进行更改，这将触发事件以更新视图模型)|2161927|entityMap|0|LINK|mutability|MUTABLE|url|http://www.orbifold.net/default/?p=550^0|0|9|0|0|0|3|2|0|O|1|0|0|4V|0|0|1G|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@$A|13|B|14|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|15|8|@$A|16|B|17|H|I]]|9|@]|C|$]]|$1|L|3|M|5|6|7|18|8|@$A|19|B|1A|H|I]]|9|@]|C|$]]|$1|N|3|O|5|6|7|1B|8|@$A|1C|B|1D|H|I]]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

<a href="http://www.orbifold.net/default/?p=550" rel="nofollow noreferrer">This site</a> has a great diagram that explains it.

Basically you have 3 components: 
1) Model - The data model of your application. this is pretty standard and the same as any MVP or MVC app. 
2) View - The XAML that defines the view/layout of your app. 
3) View Model - Because WPF demands that the view attach to things in certain ways (like requires that collections implement INotifyCollectionChanged and stuff like that) it normally requires that you massage your data a little bit to get it in a form suitable for the view to display. This is where the view model codes in. It packages up the data into view models that the view can easily display. This is what your view XAML will bind to. It must respond to events from the model layer and update itself.

(Then your controllers hang on the side somewhere - ideally using WPF commands - and make changes to the model, which fires events to update the view model)

blocks|key|255718|text|一句话？开始吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|255719|MVVM是一种UI分离模式，其中Xaml+(视图)绑定到外观(视图模型)，允许程序(模型)的内部避免UI问题泄漏到层中。|255720|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

One sentence? Here goes.

MVVM is a UI segregation pattern where the Xaml (View) binds to a facade (View Model) allowing the guts of your program (Model) to avoid having UI concerns leak down a layer.

blocks|key|5206673|text|一句话解释：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5206674|MVVM是对广受欢迎的模型-视图-展示者(+Model-View-Presenter，MVP)模式的重新构想，旨在与WPF提供的数据绑定工具很好地配合使用，从而将应用程序逻辑与UI设计分开。|5206675|更长，更有用的解释：|5206676|MVVM的基本概念是将WPF应用程序拆分成单独的组件，每个组件在屏幕上获取信息的过程中都有一个职责。|5206677|首先，你有一个模型。这是一个功能非常有限的类，通常是从一些外部源填充的，例如数据库或very服务。例如：|5206678|public+class+MessageModel
{
++++public+string+Message+{+get;+set;+}
}|code-block|syntax|javascript|5206679|在此基础上，对ViewModel进行分层，这是应用程序逻辑所在的位置，它通知视图模型的更改并确保数据一致性。通过实现INotifyPropertyChanged接口，实现了ViewModel与视图之间的双向数据绑定。|5206680|public+class+MessageViewModel+:+INotifyPropertyChanged
{
+++++private+MessageModel+_model;

+++++public+string+Message
+++++{
++++++++++get+{+return+_model.Message;+}
++++++++++set
++++++++++{
++++++++++++++if+(_model.Message+!=+value)
++++++++++++++{
++++++++++++++++++_model.Message+=+value;
++++++++++++++++++OnPropertyChanged("Message");
++++++++++++++}
++++++++++}
+++++}
}|5206681|最后，您得到了View。这是一个xaml文件，描述了用于在ViewModel中显示和编辑数据的控件的布局：|5206682|<Canvas>
+++++<TextBox+Text={"Binding+Message"}+/>
</Canvas>|5206683|之所以要进行所有这些工作，是因为模型是非常轻量级的，很容易跨域边界传递。从map服务发送或接收它或将其映射到数据库表都很简单。另一方面，ViewModel很复杂，但几乎没有依赖关系-它不关心模型从哪里获取数据，只关心它在哪里，而且它根本没有视图的概念，这使得它非常可测试(应用程序的逻辑不依赖于UI来测试)。最后，xaml被很好地划分，并且可以交给不需要了解应用程序逻辑的设计人员，只需要知道ViewModel将以特定的名称呈现特定的数据。这种封装使得在大型项目中定义角色变得非常容易，或者将有限的UI放在一起来测试逻辑，而实际的UI正在被打磨。|5206684|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

One sentence explanation:

MVVM is a reimagining of the well loved Model-View-Presenter (MVP) pattern that is designed to work especially well with databinding facilities supplied with WPF to separate application logic from UI design.

Longer, more useful, explanation:

The basic concept of MVVM is the break apart a WPF application into separate components each of which has one responsibility in the process of getting information on screen. 

Firstly you have the model. This is a class with very limited functionality that is generally populated from some outside source such as a database or webservice. For example:

<pre><code>public class MessageModel
{
 public string Message { get; set; }
}
</code></pre>

On top of that you layer the ViewModel, this is where the logic of the application sits, it notifies the view of changes to the model and ensures data consistency. By implementing the INotifyPropertyChanged interface two way databinding between the ViewModel and the view is given for free by WPF:

<pre><code>public class MessageViewModel : INotifyPropertyChanged
{
 private MessageModel _model;

 public string Message
 {
 get { return _model.Message; }
 set
 {
 if (_model.Message != value)
 {
 _model.Message = value;
 OnPropertyChanged("Message");
 }
 }
 }
}
</code></pre>

Finally you have the View. This is a xaml file that describes the layout of the controls used to display and edit the data in the ViewModel:

<pre><code>&lt;Canvas&gt;
 &lt;TextBox Text={"Binding Message"} /&gt;
&lt;/Canvas&gt;
</code></pre>

The reason that you go to all this effort is that the Model is very lightweight and easily passed across domain boundaries. It is simple to send or receive it from a webservice or map it to a database table. The ViewModel, on the other hand is complex, but has few dependencies - it doesn't care where the model gets it's data from, only that it is there and it has no concept of a view at all which makes it very testable (the logic of your application doesn't rely on a UI to test). Finally the xaml is well compartmentalised and can be handed off to a designer who needs to know nothing about the logic of the application, only that the ViewModel will present certain data under certain names. This encapsulation makes it very easy to define roles in large projects, or put together a limited UI to test logic against while the real one is being polished.

blocks|key|3093245|text|我会这样说：“用户界面与其逻辑分离的表示模式”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3093246|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would say something like: "Presentation pattern for separation of concern between user interface and it's logic"

blocks|key|254114|text|最能帮助我理解这个问题的一句简单的话是“我能不能在没有用户界面的情况下对我的业务逻辑进行单元测试？”我认为这应该是您在使用MVVM概念学习和设计时提出的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|254115|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The simple statement that helped me get my head around it best was "Could I unit test my business logic without the user interface?" I think this should be the question you ask while learning and designing using MVVM concepts.

blocks|key|3093302|text|一种改进的答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3093303|MVVM是面向未来的；您希望将应用程序逻辑从框架中分离出来，以便框架可以发展，而您的应用程序可能不需要更改，或者您的应用程序可以发展，您不必担心更改实际的UI方面。|3093304|实际上，MVVM是一种已经存在了一段时间的模式的改进。我记得当我在MFC中工作的时候，我发展了这个模式。这样做至少有两个原因。MFC或<>相当复杂，在应用程序逻辑中混入MFC结构会使应用程序变得脆弱。示例:如果支持列表/选择器内容的逻辑与操作列表/选择器本身的逻辑相结合，则用组合框(或现代术语中的选择器)替换列表框要困难得多。|3093305|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

An improved answer:

MVVM is all about the future; you want to separate your application logic from the framework so that either the framework can evolve, and your app may not have to change, or your app can evolve and you won't have to worry so much about changing the actual UI aspects.

Actually, MVVM is a refinement of a pattern that has been around for some time. I can remember evolving the pattern when I was working in MFC. There are at least two reasons for doing so. MFC or &lt;> is fairly complex, and mixing MFC constructs in with your application logic makes the application kind of brittle. Example: replacing a listbox with a combobox (or selector in modern terms) is much more difficult if the logic for supporting the content of the list/selector is combined with the logic to manipulate list/selector itself.

blocks|key|2162023|text|一种模式，其中前端(视图)和后端(模式)使用公共中介器(视图模式)进行通信(来回)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2162024|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

a pattern where the frontend(view) and backend(modal) communicates (back and forth) using a common mediator(view-modal).

blocks|key|2168161|text|MVVM模式是指UI与xaml友好的中间对象交互，以获取xaml不友好的实际数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2168162|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The MVVM pattern is when the UI interfaces with an xaml-friendly intermediate object to get at your xaml-unfriendly actual data.

blocks|key|5206860|text|一些非常好的(或接近于)一句话的解释。我只想补充说，如果你已经超过了基础水平，你想要一个如何在一个有菜单，工具栏，选项对话框，停靠工具窗口等的真实应用中使用MVVM的例子，看看SoapBox+Core和这个demo+using+SoapBox+Core。它是开源的，所以你可以得到很多想法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5206861|entityMap|0|LINK|mutability|MUTABLE|url|http://soapboxcore.com/|1|http://www.codeproject.com/KB/WPF/SoapBoxCorePinBallDemo.aspx^0|2G|C|0|2V|N|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Some really good one-sentence (or close to it) explanations already. I'll just add to it by saying that if you're past the basic level and you want an example of how to use MVVM in a real-world app that has menus, tool bar, options dialogs, docking tools windows, etc., take a look at <a href="http://soapboxcore.com/" rel="nofollow noreferrer">SoapBox Core</a> and this <a href="http://www.codeproject.com/KB/WPF/SoapBoxCorePinBallDemo.aspx" rel="nofollow noreferrer">demo using SoapBox Core</a>. It is open sourced so you can get lots of ideas.

blocks|key|5206890|text|MVVM是一种明星-粉丝关系。粉丝认识明星，但明星不认识粉丝。粉丝非常爱他的明星，如果明星改变了自己(我指的是他的着装风格)，粉丝也会相应地改变自己。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5206891|现在用"ViewModel“替换"star”，用"View“替换"fan”，再读一遍。|5206892|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

MVVM is a star-fan relationship. The fan knows the star but the star does not know the fan. The fan loves his star so much that if the star changes himself ( I mean his dressing style ), the fan changes himself accordingly.

Now replace "star" with "ViewModel" and "fan" with "View" and read it once again.

blocks|key|2168215|text|因为你不能将数据绑定到你自己的代码背后|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2168216|(这里只是半开玩笑)|2168217|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Because you can't data-bind to your own codebehind 

(only half joking here)

I heard its the next best thing in building WPF UIs, but all existing
examples have dozens of lines of code - can I get a Hello World
for MVVM that explains in no uncertain terms what its all about?
I'm fairly new to C#/.net as well, so maybe point me to some 
resources that could help too? 

Much appreciated!

One sentence explanation to MVVM in WPF?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我听说它是构建WPF UI的下一个最好的东西，但是所有现有的例子都有几十行代码--我能得到一个MVVM的Hello World吗，它明确地解释了它的全部内容？我也是C#/.net的新手，所以也许可以给我一些有用的参考资料？非常感谢！

问WPF中MVVM的一句话解释？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WPF中MVVM的一句话解释？EN