Carsten,
Nothing gets by you that's for sure...
The samples were designed to provide a working model and starting point for a developer to ramp-up quickly on the core features and usage of ASP.NET 2.0. However, the level of depth and complexity (feature-richness) is not going to be to the level of satisfying a client or production-ready application. Many of the applications do provide administrative features, as well as customizable themes and templates, etc., making them very useful as a starting point for projects.
For the survey engine, I created something as a simple yet useful application with only baseline functionality needed for the surveys to be completed and tallied up. I left room for someone to add charts, reporting, graphs, statistical analysis, etc., as they felt inclined. The dynamic number of questions was an idea I explored, but did not implement as it would potentially move into a more complex application that might slow the user down from learning the real goal, which was the asp.net 2.0 controls and features. So, for what it's worth, you are making a great assessment, but it just wasn't a requirement in our planning.
As for the direct connection to the Data Access Layer, skipping the business layer, I was not aware of this, and will have to look into it. If you are right, feel free to make the corrections as needed.
Thanks,
Shawn Livermore
MCAD, MCSD, PMP
http://www.shawnlivermore.blogspot.com
Survey Engine Arhitecture....
