Home/ Questions/Q 596627
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T16:11:30+00:00

I watched a little introduction into ASP.NET Dynamic Data, and I noticed this option

  • 0

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.

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.

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?

I’m very interested in your experiences or recommendations regarding Dynamic Data! Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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).

    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.

    The quick scaffolding is spiffy but at the end of the day I don’t think it will make web development easier.

    • 0