blocks|key|1630563|text|是的，MVVM绝对仍然是任何WPF开发的方向|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1630564|设计模式非常适合WPF框架和绑定系统的性质。如果你感兴趣的话，我在我的博客上发布了一个simple+MVVM+example。|offset|length|1630565|entityMap|0|LINK|mutability|MUTABLE|url|http://rachel53461.wordpress.com/2011/05/08/simplemvvmexample/^0|0|17|J|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Yes, MVVM is definitely still the way to go for any WPF development

The design pattern is perfectly suited to the nature of WPF's framework and binding system. I actually have a <a href="http://rachel53461.wordpress.com/2011/05/08/simplemvvmexample/" rel="nofollow">simple MVVM example</a> posted on my blog if you're interested.

blocks|key|2793111|text|Caliburn+micro是一个MVVM库，最近更新了：http://caliburnmicro.codeplex.com/不管怎样，MVVM的概念自2009年以来一直没有改变，是的，我可以投票。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2793112|entityMap|0|LINK|mutability|MUTABLE|url|http://caliburnmicro.codeplex.com/^0|T|Y|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Caliburn micro is a MVVM library recently upodated: <a href="http://caliburnmicro.codeplex.com/" rel="nofollow">http://caliburnmicro.codeplex.com/</a>
Anyway the MVVM concepts dis not change since 2009, and yes I can vote is the way to go.

blocks|key|1630591|text|是的，你的方向是对的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1630592|即使一些MVVM信息来自2009年，也有一些基于WPF+MVVM的框架会定期更新，如Caliburn+micro和MVVMLight|offset|length|1630593|我建议你花一些时间与他们中的一个，因为他们真的可以帮助编写干净的代码。我个人喜欢Caliburn+Micro。|1630594|entityMap|0|LINK|mutability|MUTABLE|url|http://caliburnmicro.codeplex.com/|1|http://mvvmlight.codeplex.com/^0|0|16|E|0|1L|9|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]|$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Yes your direction is right.

Even if some MVVM information is from 2009, there are WPF MVVM based frameworks that are regularly updated such as <a href="http://caliburnmicro.codeplex.com/" rel="nofollow">Caliburn micro</a> and <a href="http://mvvmlight.codeplex.com/" rel="nofollow">MVVMLight</a>

I suggest you to spend some time with one of them because they can really help write clean code. I personally like Caliburn Micro.

blocks|key|2879637|text|是的，MVVM就是我们要走的路。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2879638|我在我的大多数应用程序中都使用了MVVM；当我加入一家新公司时，我看到团队在过去一年的WPF应用程序中苦苦挣扎，性能、可维护性、可重用性是一些主要问题；当我查看代码时，我脑海中浮现出的唯一解决所有问题的东西就是-+MVVM。|2879639|我们对实现MVVM的代码进行了适当的重构，能够去除20-30%25的代码，重用大量代码，并将性能提高到可接受的水平。|2879640|MVVM(如果严格遵循)不仅可以帮助你正确使用WPF特性，而且会迫使你以WPF的方式来研究解决方案(而不是不使用WPF特性或者使用WinForms的方式来解决它们)，所以它对新团队来说变得更加重要和有帮助。|2879641|这里有一些我建议你回答的问题-|2879642|What+is+your+experience+with+abandoning+MVVM+for+UserControl-based+WPF+architecture?|offset|length|2879643|Starting+WPF+MVVM.+Use+a+framework?|2879644|Custom+MVVM+implementation+Vs.+PRISM|2879645|Which+WPF+control+suite+is+best+suited+to+MVVM?|2879646|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1510041/what-is-your-experience-with-abandoning-mvvm-for-usercontrol-based-wpf-architect/3163443#3163443|1|https://stackoverflow.com/questions/3606883/starting-wpf-mvvm-use-a-framework/3615938#3615938|2|https://stackoverflow.com/questions/6251821/custom-mvvm-implementation-vs-prism|3|https://stackoverflow.com/questions/3151367/which-wpf-control-suite-is-best-suited-to-mvvm/3157880#3157880^0|0|0|0|0|0|0|2C|0|0|0|Z|1|0|0|10|2|0|0|1B|3|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1A|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@$L|1D|M|1E|1|1F]]|A|$]]|$1|N|3|O|5|6|7|1G|8|@]|9|@$L|1H|M|1I|1|1J]]|A|$]]|$1|P|3|Q|5|6|7|1K|8|@]|9|@$L|1L|M|1M|1|1N]]|A|$]]|$1|R|3|S|5|6|7|1O|8|@]|9|@$L|1P|M|1Q|1|1R]]|A|$]]|$1|T|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]|13|$5|W|X|Y|A|$Z|14]]|15|$5|W|X|Y|A|$Z|16]]]]

Yes, MVVM is the way to go. 

I have used MVVM in most of my applications; When I joined a new company I saw team struggling with the WPF application they were working on from past 1 year, perfromance, maintainabilty, reusability were some major issues; when I looked at the code the only thing came to my mind for solving all the problems was - MVVM.

We refactored the code implementing MVVM properly and were able to get rid of 20-30% code, reuse a lot of code and improve performance to acceptable level.

MVVM(when strictly followed) not only helps you to use WPF features correctly but kind of forces you to look into the solution in WPF way(instead of solving them without using WPF features or using WinForms ways), so it becomes more important and helpful for new teams.

Here are some SO questions which I would suggest you to go through - 

<a href="https://stackoverflow.com/questions/1510041/what-is-your-experience-with-abandoning-mvvm-for-usercontrol-based-wpf-architect/3163443#3163443">What is your experience with abandoning MVVM for UserControl-based WPF architecture?</a>

<a href="https://stackoverflow.com/questions/3606883/starting-wpf-mvvm-use-a-framework/3615938#3615938">Starting WPF MVVM. Use a framework?</a>

<a href="https://stackoverflow.com/questions/6251821/custom-mvvm-implementation-vs-prism">Custom MVVM implementation Vs. PRISM</a>

<a href="https://stackoverflow.com/questions/3151367/which-wpf-control-suite-is-best-suited-to-mvvm/3157880#3157880">Which WPF control suite is best suited to MVVM?</a>

blocks|key|1155233|text|一般来说，任何图形用户界面架构模式都可以在WPF中实现和使用，Martin+Fowler详细解释了其中最流行的in+his+blog。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1155234|MVVM作为表示模型模式的最新阶段，是WPF的一个著名阶段，它为我们提供了开箱即用的同步状态机制，如绑定，简单的视图模型上的视图映射，如数据模板等，并且有很多使用WPF构建MVVM的例子。|1155235|但这取决于特定的项目，有时您可以很容易地按照MVP模式构建您的WPF解决方案。如果您使用的第三方WPF控件不是mvvm友好的(它们使用常规属性而不是依赖属性，因此您不能使用WPF绑定并包含许多方法，这会降低从XAML以声明方式使用控件的能力)，您应该花费额外的精力将它们应用于mvvm模式。|1155236|entityMap|0|LINK|mutability|MUTABLE|url|http://martinfowler.com/eaaDev/uiArchs.html^0|1J|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Generally speaking, any of GUI archtitecture patterns can be implemented and used with WPF, Martin Fowler explains in details most popular of them <a href="http://martinfowler.com/eaaDev/uiArchs.html" rel="nofollow">in his blog</a>.

MVVM as the latest stage of Presentation Model pattern is a famous for WPF because it provides us out of the box syncronization state mechanism like binding, simple view model on a view mapping like data template etc. and there are a lot of examples how to build MVVM with WPF.

But it depends of the particular project and some times you can easily build your WPF solution following MVP pattern, f.i. if you use third party WPF controls which are not mvvm-friendly (they uses regular properties instead of dependency properties, so you can't use WPF bindings and contains a lot of methods, that reduces ability to use control declaratively from XAML), you should spend aditional effort to adopt them to mvvm pattern.

I'm starting a new project that will be developed in WPF as a desktop application. I have spent days researching development patterns. It seems that MVVM is the way to go, as this will be an enterprise application. My concern is that all of the information I am finding is dated 2009. Can anyone tell me if this information is still valid and if I am looking in the right direction?

Thank You In Advance.

WPF Development Pattern

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在开始一个新的项目，它将作为一个桌面应用程序在WPF中开发。我花了几天时间研究开发模式。MVVM似乎是大势所趋，因为这将是一个企业应用程序。我担心的是，我找到的所有信息都是2009年的。有没有人能告诉我这些信息是否仍然有效，以及我是否在寻找正确的方向？提前谢谢你。

问WPF开发模式
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WPF开发模式EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WPF开发模式
EN