我应该将哪些模式应用于 ASP.NET MVC 区域？
为我的应用程序建模 MVC 区域的最佳方法是什么？我可以动态管理这些区域吗？它们的最佳用法是什么？
谢谢
What is the best way to model MVC Areas for my Application? Can I manage these Areas dynamically? What is the best usage of them?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
为我的应用程序建模 MVC 区域的最佳方式是什么？
区域现在已经“过时”不到一个月了（？）。我认为最佳实践尚未开发出来。 ;)
我可以动态管理这些区域吗？
您可以使用任何您想要的技术动态打开它们，但关闭它们很痛苦。如果不回收它们所在的应用程序池并再次重新注册，则无法打开和关闭区域。
它们的最佳用法是什么？
开箱即用的区域基本上是组织工具。它们可以帮助您防止 Controller 和 View 文件夹变得太大，并在保持路由配置简洁方面发挥很小的作用。
但是，使用区域来制作可共享组件，例如 可移植区域确实是一种非常杀手级的技术，它开辟了大量的划分和代码重用场景。将可移植区域视为将整个 MVC 站点从头到尾，并使其可与所有其他 MVC 站点共享。
What is the best way to model MVC Areas for my Application?
Areas have been "out" for less than one month (?) now. I don't think best practices have been developed yet. ;)
Can I manage these Areas dynamically?
You can turn them on dynamically with any technique you want but turning them off is a pain. Areas cannot be turned on and off without recycling the App Pool they are living in and re-registering again.
What is the best usage of them?
Areas out of the box are basically organisational tools. They help you keep a Controller and View folder from getting too huge and play a small part in keeping your routing configuration concise.
However using areas to make sharable components, like Portable Areas does,is a pretty killer technique that opens up a whole ton of compartmentalization and code reuse scenarios. Think of Portable Areas as taking an entire MVC site from soup to nuts and making it sharable with every other MVC site.