Castle Monorail 和 ASP.NET MVC 可以在同一个项目中共存吗？
我有一个大型单轨铁路项目，我们决定将其迁移到 ASP.NET MVC。大多数底层系统可能是可重用的，但控制器当然必须重写，可能至少需要重写一些视图。
让我印象深刻的是，一个低风险的途径是将系统中定义明确的部分逐渐转换为 MVC，或者可能转换为 MVCContrib 可移植区域。有谁知道我使用这种方法是否可能遇到任何不明显的问题？
感谢您的投入， 马修
I have a large Monorail project that we have decided we are going to move over to ASP.NET MVC. Most of the underlying system will likely be reusable, but the Controllers will of course have to be rewritten, and proabably at least some of the views.
It strikes me that a low risk avenue for this is gradually convert well defined sections of the system to MVC, and perhaps as MVCContrib Portable Areas. Does anyone know if there are any non-obvious gotchas that I am likely to run into with this approach?
Thanks for your input,
Matthew
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我突然想到：
<%= Url.Action("someaction") %>关于1.和2.也许你可以找到一些方法破解 MonoRail 并使其与 System.Web.Routing 兼容，但它不能开箱即用。
Off the top of my head:
<%= Url.Action("someaction") %>About 1. and 2. maybe you can find some way to hack MonoRail and make it compatible with System.Web.Routing, but it doesn't work out of the box.