|
Most of my work is time-constrained as my clients need data management tools yesterday. As I'm sure you can see from my blog, a lot of times, I end up using SharePoint to rapidly deliver applications, but in ASP.NET 3.5 SP1, there is a powerful new tool in my arsenal that is ASP.NET Dynamic Data.
The typical workflow for creating an ASP.NET Dynamic Data application is as follows
At this point you have the barebones for a CRUD Web application. From here you go about your normal ASP.NET development against the Entity Data Model to create the reports, visualization, services, or whatever application you were planning on.
This has accelerated numerous projects by freeing up a developer who would normally be creating and updating the data management pages to work on something far more interesting. In addition to accelerating development, it can accelerate the validation phase as well as there is a UI earlier for managing the data to ensure that everyone agrees on the data structures. If not, congratulations, you just failed fast. Make the changes to the data layer, regenerate your model, and your app is up to date.
Here are the slides for the Introduction to ASP.NET Dynamic Data at the NoVa Code Camp this summer.
