I watched a little introduction into ASP.NET Dynamic Data, and I noticed this option to create a data driven website for the first time. I have a database with a few tables, just created a Dynamic Data application out of my database and well... my application with a lot of nicely looking web pages, navigation between them and all kinds of CRUD operations was finished after 3 minutes.
我看了一些关于ASP的介绍。NET动态数据，我注意到这个选项第一次创建了一个数据驱动的网站。我有一个有几个表的数据库，刚刚从数据库中创建了一个动态数据应用程序……我的应用程序有很多漂亮的网页，它们之间的导航和各种CRUD操作在3分钟后就完成了。
OK, seriously, it isn't finished of course. There is a lot of custom logic to introduce, design to change, and also pages or relationships to remove I don't want actually to see in the web application.
好吧，说真的，当然还没有结束。有很多自定义逻辑要介绍，设计要更改，还有页面或关系要删除，我不想在web应用程序中看到。
But now I am wondering if ASP.NET Dynamic Data is at least a viable starting point or do I better start from scratch and create page by page? I could imagine that it might be useful to create a quick database maintenance web interface but is it good for a very customized web application? Is it in the end more complicated to modify the scaffold than building up everything from the ground?
但是现在我想知道ASP。NET动态数据至少是一个可行的起点，还是我最好从头开始，逐页创建?我可以想象，创建一个快速的数据库维护web界面可能是有用的，但对于一个非常定制的web应用程序来说，这是否有好处呢?最后修改脚手架是否比从地面构建所有东西更复杂?
I'm very interested in your experiences or recommendations regarding Dynamic Data! Thanks in advance!
我对你关于动态数据的经验或建议非常感兴趣!提前谢谢!
3 个解决方案
#1
1
I could never wrap my ahead around it enough to get any use out of it. At first, I thought this was Microsoft's answer to Ruby on Rails, and I was looking for the same benefit. I don't it comes close to having the same benefits. When I then compare it to a CMS (DotNetNuke, Sharepoint, Drupal, etc) it then looks really underpowered. Compared to ASP.NET MVC, it seems like going the wrong way from basic ASP.NET (MVC is removing bad abstractions from ASP.NET, while DD is adding even more abstractions).
我总不能把我的前襟绕得足够充分，使它发挥任何作用。一开始，我认为这是微软对Ruby on Rails的回应，我也在寻找同样的好处。我不觉得它有什么好处。当我将它与一个CMS (DotNetNuke、Sharepoint、Drupal等)进行比较时，它的功能就显得非常弱了。而ASP。NET MVC，看起来好像从基本的ASP走错了路。MVC正在从ASP中删除不好的抽象。NET，而DD正在添加更多的抽象)。
Personally I'd rather build something from scratch in ASP.NET MVC, though my day job is regular ASP.NET. I'm also learning Drupal as I haven't found the sweet spot with ASP.NET based CMSes. One thing at at a jobsite you're going to want to use technologies everyone else knows. So I think that limits where knowing Dynamic Data is generally useful, as basically any legacy application won't be using it and you're unlikely to find a team with existing ASP.NET Dynamic Data experience.
我个人宁愿从头开始在ASP中构建一些东西。NET MVC，虽然我的日常工作是普通的ASP.NET。我还在学习Drupal，因为我还没有找到ASP的最佳位置。基于网络的cms。在求职网站上，有一件事是你想要使用其他人都知道的技术。因此，我认为这限制了了解动态数据通常有用的地方，因为基本上任何遗留应用程序都不会使用它，而且不太可能找到一个拥有现有ASP的团队。NET动态数据的经验。
The quick scaffolding is spiffy but at the end of the day I don't think it will make web development easier.
快速搭建是非常棒的，但是最后我不认为它会使web开发更容易。
#2
1
I very like ASP.NET Dynamic Data as it is a fast way for creating data driven applications. Customization is not a complicated task.
我非常喜欢ASP。NET动态数据，因为它是创建数据驱动应用程序的一种快速方法。定制不是一项复杂的任务。
I wrote a corporate website with this technology from the scratch - it takes appr. 2 months for all. So my point of view that this is a good starting point for web applications development.
我用这个技术从头开始写了一个公司网站——它需要appr。2个月。因此，我认为这是web应用程序开发的良好起点。
#3
0
if your archetecture resembles ASP.NET Dynamic Data or DotNetNuke or some other starter kit, go for it, if
如果你的archetecture类似ASP。NET动态数据或DotNetNuke或其他入门工具，如果
- application is small to medium sized
- 应用程序小到中等大小。
- you do not have strict deadlines
- 你没有严格的截止日期
- you are learning the technology.
- 你正在学习这项技术。
otherwise or when you will be skilled in particular technology, you will prefer yourself working from scratch as it gives you more freedom and space for the implementation of ideas.
否则，或者当你精通某项技术时，你会更喜欢自己从头开始工作，因为它会给你更多的*和实现想法的空间。
For e.g, one reason for the breakthrough for Asp.Net MVC had was many .Net developers wanted freedom over the development / architecture / flow and rendering (HTML) of the product they were building. Asp.Net WebForms does provide solid and vast grounds for swift development and templates but developers had to go according to the architecture. This freedom is available under MVC and developers can make use of nearly all Libraries and skill set available and go their own way.
为e。g, Asp取得突破的原因之一。Net MVC有很多。Net开发人员想要对他们正在构建的产品的开发/架构/流程和呈现(HTML)有更多的*。Asp。Net WebForms确实为快速开发和模板提供了坚实而广阔的基础，但开发人员必须根据架构进行开发。这种*可以在MVC中使用，开发人员可以使用几乎所有的库和技能集，并按自己的方式进行。
one successful sample is *.com itself
一个成功的示例是*.com本身。
hope this helps
希望这有助于
#1
1
I could never wrap my ahead around it enough to get any use out of it. At first, I thought this was Microsoft's answer to Ruby on Rails, and I was looking for the same benefit. I don't it comes close to having the same benefits. When I then compare it to a CMS (DotNetNuke, Sharepoint, Drupal, etc) it then looks really underpowered. Compared to ASP.NET MVC, it seems like going the wrong way from basic ASP.NET (MVC is removing bad abstractions from ASP.NET, while DD is adding even more abstractions).
我总不能把我的前襟绕得足够充分，使它发挥任何作用。一开始，我认为这是微软对Ruby on Rails的回应，我也在寻找同样的好处。我不觉得它有什么好处。当我将它与一个CMS (DotNetNuke、Sharepoint、Drupal等)进行比较时，它的功能就显得非常弱了。而ASP。NET MVC，看起来好像从基本的ASP走错了路。MVC正在从ASP中删除不好的抽象。NET，而DD正在添加更多的抽象)。
Personally I'd rather build something from scratch in ASP.NET MVC, though my day job is regular ASP.NET. I'm also learning Drupal as I haven't found the sweet spot with ASP.NET based CMSes. One thing at at a jobsite you're going to want to use technologies everyone else knows. So I think that limits where knowing Dynamic Data is generally useful, as basically any legacy application won't be using it and you're unlikely to find a team with existing ASP.NET Dynamic Data experience.
我个人宁愿从头开始在ASP中构建一些东西。NET MVC，虽然我的日常工作是普通的ASP.NET。我还在学习Drupal，因为我还没有找到ASP的最佳位置。基于网络的cms。在求职网站上，有一件事是你想要使用其他人都知道的技术。因此，我认为这限制了了解动态数据通常有用的地方，因为基本上任何遗留应用程序都不会使用它，而且不太可能找到一个拥有现有ASP的团队。NET动态数据的经验。
The quick scaffolding is spiffy but at the end of the day I don't think it will make web development easier.
快速搭建是非常棒的，但是最后我不认为它会使web开发更容易。
#2
1
I very like ASP.NET Dynamic Data as it is a fast way for creating data driven applications. Customization is not a complicated task.
我非常喜欢ASP。NET动态数据，因为它是创建数据驱动应用程序的一种快速方法。定制不是一项复杂的任务。
I wrote a corporate website with this technology from the scratch - it takes appr. 2 months for all. So my point of view that this is a good starting point for web applications development.
我用这个技术从头开始写了一个公司网站——它需要appr。2个月。因此，我认为这是web应用程序开发的良好起点。
#3
0
if your archetecture resembles ASP.NET Dynamic Data or DotNetNuke or some other starter kit, go for it, if
如果你的archetecture类似ASP。NET动态数据或DotNetNuke或其他入门工具，如果
- application is small to medium sized
- 应用程序小到中等大小。
- you do not have strict deadlines
- 你没有严格的截止日期
- you are learning the technology.
- 你正在学习这项技术。
otherwise or when you will be skilled in particular technology, you will prefer yourself working from scratch as it gives you more freedom and space for the implementation of ideas.
否则，或者当你精通某项技术时，你会更喜欢自己从头开始工作，因为它会给你更多的*和实现想法的空间。
For e.g, one reason for the breakthrough for Asp.Net MVC had was many .Net developers wanted freedom over the development / architecture / flow and rendering (HTML) of the product they were building. Asp.Net WebForms does provide solid and vast grounds for swift development and templates but developers had to go according to the architecture. This freedom is available under MVC and developers can make use of nearly all Libraries and skill set available and go their own way.
为e。g, Asp取得突破的原因之一。Net MVC有很多。Net开发人员想要对他们正在构建的产品的开发/架构/流程和呈现(HTML)有更多的*。Asp。Net WebForms确实为快速开发和模板提供了坚实而广阔的基础，但开发人员必须根据架构进行开发。这种*可以在MVC中使用，开发人员可以使用几乎所有的库和技能集，并按自己的方式进行。
one successful sample is *.com itself
一个成功的示例是*.com本身。
hope this helps
希望这有助于