At the risk of misinforming the sound, I believe that it is mostly useful for RAD and quick drawing applications.
It feels a little Ruby-esque in the sense that it will mask almost everything you need from a CRUD application. It’s easier to work for us, right; and most people are not wiser.
I am pretty green in the workplace, I'm just starting to work on the actual work as a developer (cells and free coffee), so my opinions may be a little on the green side, but I would like some comments from other older people.
Is it somewhere between MVC2 (base scaffolding) and Microsoft Lightswitch (wizard based development)? Should I reissue?
One of the best uses I've heard for Dynamic Data was to quickly create a Django-like admin section for the site. It does not have to be “perfect” as it is not intended for users, but it gives you pleasant convenience and is easy.
Personally, I like to use dynamic data for administration pages, those pages that no one actually sees, but should be available for use by some admin users. Previously, they made some efforts for the development team to combine them, but with Dynamic Data it's almost out of the box.
Tailspin travel, MVC 2, , , .
, Dynamic Data , "ASP.NET-". , , ASP.NET.
Admin, " " "" . , , , , . , , , , /. , . - , , , .. , - .
( ), (HUGE time saver) " ". - - , , Dynamic Data, , .
, , . , , , . .
, , . , , , / .. /. "" , .NET, , , / , . , SQL , GridViews ..