实体框架代码优先：应该用作生产技术还是仅用于测试目的？
正如标题所说，这种技术应该仅用于测试目的还是可以用于任何人都可以使用的程序中？
感谢您的任何建议。
As the title says, should this technique be used only for test purposes or could it be used in programs that will be used by anyone?
Thanks for any suggestion.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
它很好，经过测试，可以用于任何类型的测试、部署或生产目的。不过，我同意 @Betty 不使用数据库删除/重新创建功能的意见。因为数据库中的一个小故障可能会让您丢失所有数据。
我已经在我的 Asp.net 项目中使用了它，该项目目前已上线一个月左右，并且它的工作魅力。微软已经做出了令人惊奇的事情，你不应该担心。这是一个完整的项目，如果有什么的话，只会添加高级功能，而不会添加其他任何东西。
It's good and tested and ready for any kind of testing or deployment or production purposes. Though, I would second the opinion of @Betty of not using the database dropping/recreating functionality. Since a minor glitch in the database might make you lose all your data .
I have used this in my Asp.net project which is currently online for a month or so and it's working charm. Microsoft has pulled amazing thing and you shouldn't worry about. It's a complete project, if anything only advance features will be added and nothing else.
我不建议在生产中使用数据库删除/重新创建功能，因为您会在此过程中丢失数据。
然而标准模型->数据库映射和查询的东西都很好。
I wouldn't recommend using the database dropping/recreating functionality in production as you lose your data in the process.
However the standard model -> db mapping and querying stuff is all good.
这是一个功能齐全、经过测试的版本，而不是 CTP 或测试版。为什么它不能在生产环境中使用？您是否想要在生产环境中使用它完全取决于您和您的团队。
It's a fully featured, tested release, not a CTP or beta. Why wouldn't it be ready to use in a production environment? Whether you want to use it in a production environment is entirely up to you and your team.