CustomDataSource not part of the CompositeWeb

Topics: Web Client Software Factory
Nov 8, 2006 at 1:30 AM
In the reference application, is there a (future) reason that the CustomDataSource folder is part of the reference app instead of the CompositeWeb library code? In my testing application I've cut it out and added it to the CompositeWeb project and it seems more logical there than duplicated in each project unless you know something we don't...

Nov 8, 2006 at 3:10 PM
Hi Adam,

Our general approach is to create code in the reference implementation to solve a user story, then move it out as it becomes apparent that it should be shared across applications. "Moving it out" might result in moving something to an application block, or, it could be something that is automatically generated as part of a solution when we introduce the guidance package. We will be looking at the custom datasource control later this week, or possibly next week. That's good feedback with your experience, which helps us with prioritization and strategy.