MVVM 框架和 Prism 4？
我刚刚读了这个问题。它有一些很好的答案，但它们已经存在一年多了，并且去年这个领域发生了很多变化。一些最流行的框架已经在新的主要版本中出现，例如 Prism 和 MVVM Light Toolkit。
我的问题在某种程度上是相同的，但有一点不同，由于区域和模块功能，我已经在使用 Prism 4.0。
Prism 4.0拥抱了MVVM，但我觉得有些东西“不轻量”，例如交互请求。 所以我在想使用另一个 MVVM 框架作为 Prism 4.0 的替代品或补充会更好吗？
I just read this question. It has some nice answers, but they are over 1-year-old, and a lot have changed in this space over the last year. Some of the most popular frameworks have come out in a new mayor release such as Prism and MVVM Light Toolkit.
My question is somehow the same, but with one twist, I'm already using Prism 4.0 because of the region and module features.
Prism 4.0 embraces MVVM, but I feel there are some things which are "not lightweight", for instance interaction requests.
So I'm thinking would it better to use another MVVM framework either as a substitute or a supplement for Prism 4.0?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
除了 Prism 之外，没有什么可以阻止您使用 MVVM 框架。我们使用的是 Caliburn.Micro 和 Prism - 提供的功能有一些交叉，也有很多差异。使用最适合您要解决的问题的工具。
There's nothing to stop you using an MVVM framework in addition to Prism. We're using Caliburn.Micro and Prism - there is some crossover in functionality provided, and many differences too. Use whatever tool is most appropriate for the problem you're solving.
MVVMLight 正在迅速成为标准的 MVVM 实现。特别是由于它的多平台支持（wpf、silverlight、wp7）、极高的可混合性，以及制作 MVVM 应用程序所需的东西……仅此而已……仅此而已。
MVVMLight is quickly becoming the standard MVVM Implementation. In particular due to its multi platform support (wpf, silverlight, wp7), extreme blendability, and exactly the stuff you need to make MVVM applications ... nothing more ... nothing less.