Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 14, 2008 07:08 PM by marcind
Mar 08, 2008 06:24 AM|LINK
Despite reading the term scaffolding many times, I am still unsure what the difference is. In particular, how much more do you need to code for non-scaffolded pages?
Mar 10, 2008 06:54 PM|LINK
My understanding of scaffolding is this. Scaffolding refers to the automatic generation of the CRUD UI for all tables that are represented in your DBML file. So, if you turn scaffolding on in the Global.asax file, it will create the templated UI for you.
There are pros and cons to be considered: security, unneeded "pages" created, etc. You may want to customize the look of pages or fields, which will mean that you should override the default page(s) created by scaffolding with your own custom representation.
This screencast can help you with these.
Mar 13, 2008 10:34 AM|LINK
Thanks for this. I since found a great post here
http://blogs.msdn.com/brada/archive/2007/12/13/asp-net-3-5-extensions-all-about-dynamic-data.aspx to answer this completely
Mar 14, 2008 07:08 PM|LINK
Scaffolding in the sense used by Dynamic Data refers to automatically creating a CRUD user interface based solely on a data model generated by an ORM technology such as LINQ to SQL. Dynamic Data itself does not generate any code based on the model. Instead,
the UI is based on a set of page and field templates. The Dynamic Data framework reflects on the model and then modifies and tweaks the templates at runtime on a per-request basis to display UI for a particular table being requested. The benefit of this (compared
to solutions that generate a bunch of pages) is that you can easily get a full CRUD UI (as demonstrated in David's blog) while being able to globally modify the bahavior of all your pages.
Let us know if you have any other questions.