The module I am writing consists of a multiview with some single views inside, each of them representing/displaying different sets of information, e.g.:

{multiview}

• View 1: List of employees
• View 2: Details of an employee
• View 3: List of jobs
• View 4: Job details
• View 5: List of birthdays
• View 6: List of anniversaries

{/multiview}

I am doing it this way so the module can be placed anywhere on the site and then the user can select in the module instance settings which information he wants to display on that place. But I am wondering if this is a good way, asking myself how the views and other parts of the ASCX are loaded. Even only one single view displayed a time, are all other views loaded together so it could be a performance issue? What about all my SqlDataSources which are not inside one of the {view}...{/view} tags? Does it mean everytime a single view is displayed, all SqlDataSources are loaded too? Should I better break all functionalities up into multiple modules?

Hi Erik,

I think I wasn't clear enough: Talking about a "view" I mean the <asp:view> within an <asp:multiview>. Currently I have one user control (myModuleView.ascx) which looks like this

1. only that <asp:view> is loaded, which is set to visible, or if every module instance will actually load all of the <asp:view> and then simply hide those not set to visible,
2. all of the <asp:SqlDataSource> will be loaded, as they are not inside one of the <asp:view>