ASP.NET动态数据专业版和缺点 [英] ASP.NET Dynamic Data PRO and CONS

问题描述

我听说过ASP.NET 4中的ASP.NET动态数据.

I heard about ASP.NET Dynamic Data in ASP.NET 4.

我想知道您是否已经在真实场景的Web应用程序中实现了您的意见，尤其是在定制方面.

I would like to know if you have implemented in real scenario web application and your opinions, specially in terms of customization.

一些问题:

• 我可以使用自定义逻辑来验证字段吗?
• 当用户按下特定表的DELETE按钮时，是否可以添加逻辑?

乍一看，构建脚手架似乎很容易，但是有任何缺点吗?

As at a first look, it seems very easy build Scaffolding but any Cons?

感谢您的宝贵时间！ 问候

Thanks for your time! Regards

推荐答案

我主要使用动态数据来创建仅限开发人员"的后端管理工具，我需要在其中直接访问数据库.为此，它非常方便且非常快速地使用.

I've mostly used Dynamic Data to create "developer only" back-end admin tools, where I need to access the database directly. For that purpose it's very convenient and extremely fast to use.

MSDN上有几篇有关自定义动态数据的文章: ASP.NET动态数据层自定义:验证数据字段.我确信它足够灵活，可以满足您的要求.

MSDN has several articles on customizing Dynamic Data: ASP.NET Dynamic Data Layer Customization: Validating Data Fields. I'm sure it's flexible enough to meet your requirements.

关于优缺点，这实际上取决于您要构建的内容.实现自定义设计和功能的时间可能与从头开始实施项目的时间一样长(无论您使用哪种脚手架框架). 因此，如果您的项目是基本的数据输入应用程序，请使用动态数据.如果它是面向客户的网站，我认为您最好使用ASP.NET Webforms或MVC.话虽如此，DD仍然非常适合从浏览器访问数据.

As for pros and cons, it really depends on what you're building. Implementing custom designs and functionality can end up taking just as long as it would've implementing the project from scratch (regardless of what scaffolding framework you use). So if your project is a basic data entry app, go with Dynamic Data. If it's customer-facing site, I think you're probably better off using ASP.NET Webforms or MVC. But that said, DD is still very handy for just accessing the data from a browser.

这篇关于ASP.NET动态数据专业版和缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！