Not sure how many out there have played around with .NET Dynamic Data, but I found it to be a thought-provoking approach. If you’ve built your relational database well, it allows for RAD in the beginning. I haven’t quite figured out yet what you’d do in the case of a data schema change…rebuild it maybe? I also like the built-in asp.net routing feature, and the UI consistency across all object CRUD operations is nice. I’m not sold though on this being the sole development model for an enterprise site, but if mixed in with classic web forms or MVC one might experience the best of all worlds.
http://msdn.microsoft.com/en-us/magazine/gg535665.aspx
If you want to build a sample site, following the example you’ll need the Adventure Works DB if you don’t already have it:
http://msftdbprodsamples.codeplex.com/releases/view/37109
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment