在 Prism 和 Caliburn 之间进行选择
我在个人项目中使用 Prism 2.0 已有几个月了。我最近听说了 Caliburn，想知道是否有令人信服的理由让我考虑它。
我喜欢 Prism 的动态模块加载能力。我打算为我的应用程序构建模块，并希望能够以模块化方式部署它们。 Caliburn 也可以做到这一点吗？
Caliburn 相对于 Prism 有何优势？
（我了解到 Prism 也将在 2010 年 9 月推出一个新版本，该版本将利用 .Net 4.0。并且我的应用程序也将保持灵活，以便到那时进行更新。）
I have been using Prism 2.0 for a personal project for a few months now. I have recently heard of Caliburn and am wondering if there are compelling reasons for me to consider that instead.
I like Prism's dynamic module loading capability. I intend to build modules for my application and would like to be able to deploy them in a modular manner. Is that also possible with Caliburn?
What are the advantages of Caliburn over Prism?
(I read that Prism will also have a new version by September 2010 that will leverage .Net 4.0. and am keeping my application flexible to be updated by then as well.)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Prism 和 Caliburn 是互补的框架。当您专注于 WPF 中的 MVVM 时，Caliburn 确实可以实现许多缺点，而 Prism 则可以实现良好的模块化（除其他外）。这是一种简化（两者都具有更多的功能），但这是您想要将它们组合起来的主要原因。
Caliburn 具有内置的 Prism 支持，因此您可以同时使用两者。这是我发现的一篇文章，其中有人使用集成来设置他们的第一个模块。
http://rauhski.blogspot.com/2009/10 /build-application-with-caliburn-and.html
另外，如果您下载 Caliburn，其中包含一个演示 Prism 集成的示例。
Prism and Caliburn are complimentary frameworks. Caliburn really enables a lot of the things that are shortcomings when you focus on MVVM in WPF and Prism allows that nice modularity (among other things). This is a simplification (both have way more features than just that), but it's the major reason you'd want to combine them.
Caliburn has builtin Prism support so you can use both. Here's an article I found of someone using the integration to setup their first module.
http://rauhski.blogspot.com/2009/10/build-application-with-caliburn-and.html
Also, if you download Caliburn, there is a sample included that demonstrates the Prism integration.