Well, the strange thing is that the error rendering the control only happens in the Design View, but not at run time.
The design time error is however very inconvenient, because it makes it impossible to use the property editors of the CreateUserWizard so that the properties of other Wizardsteps can not be designed or changed.
Well, if I would have only 1 wizardstep with a MultiFormView I could work arround this bug by editing the properties of the other steps first, but in fact I need more then one wizardstep with MultiFormView.
Of course I can also work arround this by using a FormView instead of the .netTiers MultiFormView, but that was not my purpose.
I wanted to use the MultiFormView to reuse the insert templates by referencing their paths, instead of doing copy and paste and have double implementations of the same script code.
The datasource control is placed outside of the CreateUserWizard control on the same page, see below:
<
asp:Content ID="Content1" ContentPlaceHolderID="Main" runat="Server">
<div id="col_mid_page">
<br />
<asp:CreateUserWizard ID="CreateUserWizard1" runat="server">
<WizardSteps>
<asp:WizardStep ID="step1" runat="server" Title="Add Company Info">
<data:MultiFormView ID="FormViewTest2" runat="server" AllowPaging="false" DataKeyNames="BedrijfID"
DataSourceID="BedrijfDataSource1" DefaultMode="Insert">
<InsertItemTemplatePaths>
<data:TemplatePath Path="~/Admin/UserControls/BedrijfFields.ascx" />
</InsertItemTemplatePaths>
</data:MultiFormView>
</asp:WizardStep>
<asp:CreateUserWizardStep ID="step2" runat="server">
</asp:CreateUserWizardStep>
<asp:CompleteWizardStep ID="step3" runat="server">
</asp:CompleteWizardStep>
</WizardSteps>
</asp:CreateUserWizard>
<data:BedrijfDataSource ID="BedrijfDataSource1" runat="server" SelectMethod="GetByBedrijfID">
</data:BedrijfDataSource>
</div>
</
asp:Content>