MVC 3 与 MVC 涡轮机
我在 MVC 2 中实现了自己的控制反转方法。我正在考虑回顾 MVC Turbine 并可能转向它。然而，我今天注意到 MVC 3 Preview 1 已经发布，并且内置了新的控制反转支持。我知道它发布还需要一段时间，但想看看是否有人知道新的控制反转支持是否会基本上使 MVC Turbine 变得不必要。
你怎么认为？
I have implemented my own inversion of control methodology in MVC 2. I was thinking of reviewing MVC Turbine and possibly switch to that. However, I noticed today that MVC 3 Preview 1 has been released and has new inversion of control support built in. I know it will be a while before it is released, but wanted to see if anyone knows if the new inversion of control support will basically make MVC Turbine unnecessary.
What do you think?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
尽管 MVC3 功能与 MVC Turbine 当前提供的功能重叠（过滤器支持、控制器注入等），但我预计 MVC Turbine 不会因此而消失:)
我的目的是提供与 MVC Turbine 当前提供的新功能相同的功能MVC3 位由于框架的新增功能缓解了 MVC Turbine 在 MVC1 和 MVC2 中必须克服的一些摩擦。
随着 MVC3 位的巩固，MVC Turbine V3 处理 DI/IoC 支持的最终功能也将得到巩固。本质上，MVC Turbine 将发展为 ASP.NET MVC 应用程序提供组合支持，并依靠 MVC3 的 DI 功能来实现“幕后”管道。
如果您对当前在 MVC1/2 应用程序中最佳使用 MVC Turbine 有任何疑问，请随时与我联系或 ping Google 网上论坛了解信息。
Although MVC3 features overlap those that MVC Turbine currently provides (filter support, controller injection, etc.), I do not foresee MVC Turbine going away because of that :)
My intent is to provide the same features that MVC Turbine currently offers with the new MVC3 bits since the new additions to the framework provide ease some of the friction that MVC Turbine had to overcome in MVC1 and MVC2.
As the MVC3 bits solidifies, so will final features of MVC Turbine V3 that deal with DI/IoC support. Essentially MVC Turbine will evolve to provide composition support to ASP.NET MVC applications and lean on the DI features of MVC3 for the 'under the covers' plumbing.
If you have any questions with regards to best currently utilize MVC Turbine with your MVC1/2 applications don't hesitate to contact me or ping the Google Group for information.
MVC Turbine 不仅仅提供 IoC 支持。它更多的是关于组合、组件发现和自动注册功能（因此与 MEF 的重叠比 MVC3 DI 功能更多:)。
MVC Turbine is not about just providing IoC support. It is more about composition, components discovery and auto-registration capabilities (thus more overlapping with MEF than MVC3 DI features :).