问题描述
我很好奇，在典型的心态中，我们可以建立一个其他人可以开发插件的平台。
I was curious how in the typical ASP.NET MVC mentality one could build a platform that others could develop plugins for. I mean, how would those plugins look like?
像退出WebForms的用户控件一样，封装所有图层本身或者表示模型的三个不同文件的视图和控制器。我应该开发的核心，我希望其他人为以后创建插件上。哪种心态会更好，经典的Web窗体或ASP.NET MVC？
Like exiting user controls for WebForms, encapsulating all layers in themselves, or three different files representing the model the view and the controller. I should develop the core of a CMS, that I'd like others to build plugins for later on. Which mentality is better for that, classic Web Forms or ASP.NET MVC?
我需要开发人员能够单独构建组件。是否可能将MVC目录结构封装在组件DLL文件中，然后当我引用DLL文件时，能够直接访问组件的模型，视图或控制器作为一般MVC结构的一部分？
I need developers to be able to separately build components for that. Is it possible to encapsulate the MVC directory structure in a component DLL file and then when I reference the DLL file, to be able to directly access the component's model, view, or controller as part of the general MVC structure?
推荐答案
最有希望的组件技术来自于我们在lostechies.com和Mvccontrib以。可移植区域允许将整个MVC应用程序附加到现有应用程序上。因此，它不仅仅是一个UI组件，还提供了所有的工作流程和屏幕集成。
The most promising component techniques have come from the guys over at lostechies.com and Mvccontrib in the form of Portable Areas. Portable Areas allows an entire MVC app to be appended onto an existing application. So its not just a UI component but also provides all the work flow and screen integration as well.
也有类似这样的。我不知道如何，但它是插件和播放。
Open Forum does something like this as well. I don't know how, but it is very plug and play.
对于直接的插件架构，有一个有趣的截屏和源代码为Rob Connery的。他利用App-Code目录将新插件插入到位，而无需编辑主网站。
For straight up plugin architecture there is an interesting screencast and source code for Rob Connery's link text. He takes advantage of the App-Code directory to slide new plugins into place without having to edit the main site.
这篇关于自定义组件和ASP.NET MVC的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！