MVVM Light for Finanace 产品是否由大约 40 个模块构建？
只是想知道我是否应该继续使用 MVVM light 来构建 Enterpside 产品？我在某处读到 MVVM 适合启动小型应用程序，而 Prism 适合组合应用程序。您能解释一下这是什么意思吗？我只是不想依赖像 prism 这样的大型框架，因为有时它会接管您的控制权，让您可以选择遵循其开发方法。我认为 MVVM Light 简单又方便，但我想知道它是否可以用于构建基于组合的应用程序，或者是否有一些东西我们可以扩展它以添加组合来构建产品模块。 我希望我的问题很清楚
Just wondering should I be going on using MVVM light to buidl enterpside product? I read somewher MVVM is good for starting of small apps and Prism is good for composite apps. Can you please explain what does this mean? I just don't want to have dependency on huge framework like prism as sometimes it takes over the control from you leaving with you the option of following its development methodology. I think MVVM Light is simple and handy but jsut wanted to know whether it can be used in building composition based application or is there something out there where we can extend it to add composition to build modules of the product.
I hope my question is clear
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
首先MVVM light适合企业应用程序。但是，它是一个工具包，而不是一个完整的框架，因此如果您需要组合，则必须自己构建它。您可以向 MEF 寻求支持。
另一方面，Prism 是一个基于 MVVM 模型和 MEF 的著名作品。它具有内置的组合，您不必自己实现它。
因此，这取决于您选择哪一个企业应用程序的范围和属性。
First of all MVVM light is suitable for enterprise apps. However, it is a toolkit and not a full fetched framework, so if you need composition you will have to build it yourself. You could draw on MEF for support.
Prism on the other side is a fameworkthat builds on the MVVM model and the MEF. It has composition on board and you do not have to implement it on your own.
So it depends non then scope and the properties of your enterpise application which one you choose.
你的问题中有一些误解。
首先，您提到的所有技术都不是相互排斥的。可以使用 Prism、MEF 和 MVVM Light 工具包构建应用程序。
其次，如果您正在开发 WPF 应用程序，那么您应该使用 MVVM 设计模式您决定采用哪些技术。
Prism 实际上在应用程序设计中占用的空间相对较小。这些功能和组件本质上是选择性加入的。使用你需要的部分并忽略你不需要的东西。事实上，与 SCSF 相比，Prism 实际上设计得很好。
可以说，Prism 和 MEF 存在一些重叠的目标，但这已在此处进行了讨论< /a>
There are a couple of misconceptions in your question.
First of all none of the technologies you've mentioned are mutually exclusive. An appliction could be built using Prism, MEF and the MVVM Light toolkit.
Secondly, if you're developing a WPF application then you should be using the MVVM design pattern regardless of which technologies you decide to incorporate.
Prism actually has a relatively small footprint in an applications design. The features and components are essentially opt-in. Use the bits you need and ignore the stuff you dont need. Indeed, compared to the monstrosity that was SCSF, Prism is actually well designed.
There are arguably some overlapping goals of both Prism and MEF but this has been discussed here