什么是ASP.NET MVC项目和extensionable /皮肤系统的最佳做法？ [英] What is best practice on ASP.NET MVC projects and extensionable/skinned systems?

问题描述

我一直在想打造在MVC项目的最佳做法，让别人创建扩展/模块/插件和皮肤/主题等吧。

I've been wondering about best practices on creating a project in MVC, and let others create extension/modules/plugins and skins/themes etc, for it.

例如字preSS为大这个。只要上传一个文件或文件夹。甚至可以直接从你的WP管理浏览插件，并通过简单的点击安装。

For example WordPress is great at this. Just upload a file or folder. Or even browse the plugins directly from your WP administration and install by a simple click.

在这里是否有人有关于如何创建一个项目，它允许灵活的一些提示。
对于皮肤，我可能需要实现我自己的ViewEngine，对吧？

Does anybody here have a few tips on how to create a project that allows that flexibility. For the skins I might need to implement my own viewengine, right?

任何好的资源和技巧将是巨大的。

Any good resources and tips would be great.

谢谢！

推荐答案

我最终使用的VirtualPathProvider因为我想在应用程序之外的意见。现在，我们把它可能为次要存储在数据库中。

I ended up using a VirtualPathProvider since I wanted the views outside of the application. Now, we made it possible for the views to be stored in the database.

这篇关于什么是ASP.NET MVC项目和extensionable /皮肤系统的最佳做法？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！