我知道 MEF 是微软推荐的可插拔应用框架，但也许一些 IoC 框架也可以帮助你。 MS 推荐的是 Unity（根据 Microsoft Patterns and Praciticies 开发）codeplex 上的 unity
I know MEF as MS recomended framework for pluggable aplications, but maybe some IoC framework can helps you also. Recommended by MS is Unity (developed under Microsoft Patterns and Praciticies) unity on codeplex
I have used HTML, WinForms, ASPX, WPF, WCF, Web service, Silverlight, PRISM, MEF for applications in the last few years and my personal choices (given no restraints on a new project) would be:
WPF or Silverlight (Update: I would swing more towards WPF, now that Silverlight is no longer broadly supported)
WCF services
A modular framework like PRISM (which now includes MEF)
PRISM is the biggest gain as the components you build really are loosely coupled and modules can be developed independently without developers breaking each other's code.
For something specific like a dental practice hopefully you will be able to build a layer on top of general purpose plugin frameworks.
The plug-ins, and their container, should be specialized for the domain. The best way to identify what that that specialization should be is to enumerate several plug-ins that would be appropriate for this software, recognize what is common amongst them and abstract/represent them in your framework.
I know this is not very concrete but hopefully somewhat useful.
发布评论
评论（4）
托管扩展性框架内置于 .NET 4.0 中，可从CodePlex 作为早期版本的 dll。
The Managed Extensibility Framework is built into .NET 4.0, and is available from CodePlex as a dll for earlier versions.
我知道 MEF 是微软推荐的可插拔应用框架，但也许一些 IoC 框架也可以帮助你。 MS 推荐的是 Unity（根据 Microsoft Patterns and Praciticies 开发）codeplex 上的 unity
I know MEF as MS recomended framework for pluggable aplications, but maybe some IoC framework can helps you also. Recommended by MS is Unity (developed under Microsoft Patterns and Praciticies) unity on codeplex
在过去的几年里，我在应用程序中使用过 HTML、WinForms、ASPX、WPF、WCF、Web 服务、Silverlight、PRISM、MEF，我个人的选择（不限制新项目）是：
PRISM 是最大的收获，因为您真正构建的组件是松散耦合的，模块可以独立开发，而无需开发人员破坏彼此的代码。
I have used HTML, WinForms, ASPX, WPF, WCF, Web service, Silverlight, PRISM, MEF for applications in the last few years and my personal choices (given no restraints on a new project) would be:
PRISM is the biggest gain as the components you build really are loosely coupled and modules can be developed independently without developers breaking each other's code.
对于像牙科诊所这样的特定事物，希望您能够在通用插件框架之上构建一个层。
插件及其容器应该专门针对该域。确定该专业化的最佳方法是枚举适合该软件的几个插件，识别它们之间的共同点并在您的框架中抽象/表示它们。
我知道这不是很具体，但希望有点用。
For something specific like a dental practice hopefully you will be able to build a layer on top of general purpose plugin frameworks.
The plug-ins, and their container, should be specialized for the domain. The best way to identify what that that specialization should be is to enumerate several plug-ins that would be appropriate for this software, recognize what is common amongst them and abstract/represent them in your framework.
I know this is not very concrete but hopefully somewhat useful.