简体   繁体   English

asp.net mvc 2 RC已准备好生产

[英]is asp.net mvc 2 RC is ready for production

在生产中使用asp.net mvc 2是否存在任何风险,或者坚持使用asp.net mvc 1。

It is (ready). 已经准备好了。 Telling that from experience. 从经验上讲。

Most trouble are with 3rd party tools (ie - spark hack ). 最麻烦的是第三方工具(例如-spark hack )。

Took me like 1 day to migrate completely our web app to Mvc2 RC (which ain't giant). 我花了整整1天的时间将我们的Web应用程序完全迁移到Mvc2 RC(这不是很大)。

Asp.net Mvc has quite nice suite of unit tests and really good architecture - therefore, it's kind a stable, there aren't much breaking changes (faced only one in Mvc2 RC => viewcontext demands textwriter as last argument or something. Normally - that shouldn't be a problem and you wouldn't even notice that (not for me, cause i had mechanism that renders html as string). And there might be some issues with validation (our app is quite read-only )). Asp.net Mvc具有相当不错的单元测试套件和非常好的体系结构-因此,它是一种稳定的,没有太多重大更改(在Mvc2 RC中仅面对一个=> viewcontext要求将textwriter作为最后一个参数或其他内容。通常-那应该不成问题,您甚至不会注意到(对我而言,不是,因为我有将html呈现为字符串的机制)。并且验证可能存在一些问题(我们的应用程序是完全read-only ))。


Related blog post from our fellow member Craig. 我们的成员Craig的相关博客文章 :) :)

Recently (current date => 2010-02-06) Mvc2 RC2 was announced . 最近(当前日期=> 2010-02-06) 宣布了Mvc2 RC2

Main changes - validation 主要变更-验证

There will always be risks. 总会有风险。 The RC version is not officially supported by Microsoft, so if you go that way you will have to rely on the community (which btw is great). RC版本不受Microsoft官方支持,因此如果您采用这种方式,则必须依靠社区(顺便说一句很棒)。 The other risk is that some features might change in the RTM and if you'd like to upgrade you may need to retest the whole application. 另一个风险是RTM中的某些功能可能会更改,如果要升级,则可能需要重新测试整个应用程序。

Other than that the ASP.NET MVC 2 RC comes with a go-live license so you could use it in a production environment. 除此之外,ASP.NET MVC 2 RC带有上线许可证,因此您可以在生产环境中使用它。

If you have quality processes to test your application then I don't see a problem with it. 如果您有质量好的流程来测试您的应用程序,那么我认为它没有问题。

I think a better question is do you want to be developing on such a recent release. 我认为一个更好的问题是您是否希望在这样的最新版本上进行开发。

  • You will find less documentation. 您会发现较少的文档。
  • You may find problems with the framework during development. 在开发过程中,您可能会发现框架存在问题。
  • You may find small breaking changes (only) when you update to later revisions. 当您更新到更高版本时,您可能会发现微小的重大更改(仅)。

In the end the source code is available if you really need to fix any problem you find in the framework. 最后,如果您确实需要解决在框架中发现的任何问题,则可以使用源代码。 You just need to decide if you want to develop with the newer features or on a more understood and documented version. 您只需要决定是要使用更新的功能还是要使用更易于理解和记录的版本进行开发。

For me, I'm moving to version 2 as soon as I find the time. 对我来说,我会在发现时间后立即转向版本2。

This RC build does not have a go-live statement, so it is not supported by Microsoft. 此RC内部版本没有上线声明,因此Microsoft不支持。 You need to wait till its final release. 您需要等待其最终发布。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM