I looked at a small introduction to ASP.NET dynamic data, and I noticed this option for creating a data driven website. I have a database with several tables, just created a Dynamic Data application from my database and well ... my application with a lot of beautiful looking web pages, navigation between them and all kinds of CRUD operations was completed in 3 minutes.
Well, seriously, it's not over, of course. There are many customizable logic for embedding, design changes, and also pages or relationships for deletion that I don't want to see in a web application.
But now I wonder if ASP.NET Dynamic Data is at least a viable starting point or is it better to start from scratch and create page by page? I could imagine it would be useful to create a web interface for quick database maintenance, but is this good for a very customized web application? In the end, is it more difficult to modify the scaffold than to build everything from the ground?
I am very interested in your impressions or recommendations regarding dynamic data! Thanks in advance!
source
share