我应该为新的 CRUD asp.net 应用程序使用 SubSonic 还是动态数据?
我需要构建一个快速 CRUD asp.net 站点,但这可能会成为一个更大的应用程序。 我对 SubSonic 有一些经验,但自从我用它做过项目以来已经很久了,我必须重新学习它。 我也在考虑使用动态数据。 有没有人对这些工具有任何经验可以告诉我应该走哪条路?
I need to throw together a quick CRUD asp.net site, but this may become a bigger application down the road. I have some experience with SubSonic, but it has been so long since I did a project with it I have to relearn it. I am also considering using Dynamic Data. Does anyone have any experience with these tools that can tell me which way I should go?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

发布评论
评论(4)
~没有更多了~
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
这些天我几乎在所有事情上都使用亚音速。 SubSonic 的优点是,如果您以后需要增强/扩展它,您可以在其上构建任何您想要的抽象层 - 它实际上只服务于一个主要目的 - 消除创建 CRUD 代码的麻烦。
我没有广泛使用动态数据,但从我所读到的内容来看,它似乎为您创建了很多脚手架,并且它可能无法与更广泛的应用程序很好地混合。 如果您需要未来的可扩展性,我建议使用亚音速,但对于严格用于通过网络维护数据库的短期一次性应用程序来说,动态数据可能是一种选择。
I use subsonic for almost everything these days. The advantage of SubSonic is that you can build whatever abstraction layer you want on top of it, if you need to enhance/extend it later - it really only serves one main purpose - taking the crap out of creating crud code.
I've not used dynamic data extensively, but from what I've read, it seems like it creates a lot of the scaffolding for you, and it might not mix well with a more extensive application. If you need future extensibility, I'd recommend subsonic, but dynamic data may be the way to go for short one-off applications strictly used to maintain a database via the web.