ASP.NET designer fails to auto-generate fields

ASP.NET designer fails to auto-generate fields by Andrew Petrochuk

Active

Type:	Bug
ID:	534340
Opened:	2/17/2010 1:49:20 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

ASP.NET designer fails to auto-generate fields that are part of WizardSteps for asp:Wizard contol.

Example:
        <asp:Panel runat="server" ID="panel1">
            <asp:TextBox runat="server" ID="textBox1"></asp:TextBox>
        </asp:Panel>
        <asp:Wizard runat="server" ID="wizard">
            <WizardSteps>
                <asp:WizardStep runat="server" ID="step1">
                    <asp:TextBox runat="server" ID="textBox2"></asp:TextBox>
                </asp:WizardStep>
            </WizardSteps>
        </asp:Wizard>

textBox1 field is generated. textBox2 is NOT generated in *.aspx.designer.cs

Details (expand)

English

Visual Studio 2010 Release Candidate

Windows Vista

English

Paste this code on new aspx page
<asp:Panel runat="server" ID="panel1">
            <asp:TextBox runat="server" ID="textBox1"></asp:TextBox>
        </asp:Panel>
        <asp:Wizard runat="server" ID="wizard">
            <WizardSteps>
                <asp:WizardStep runat="server" ID="step1">
                    <asp:TextBox runat="server" ID="textBox2"></asp:TextBox>
                </asp:WizardStep>
            </WizardSteps>
        </asp:Wizard>

textBox1 field is generated. textBox2 is NOT generated in *.aspx.designer.cs

textBox2 is generated in *.aspx.designer.cs

0 attachments

Posted by Microsoft on 3/5/2010 at 2:34 PM

A patch for this issue for Visual Studio 2010 RC is now available for download:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=27117

Posted by Microsoft on 2/18/2010 at 11:41 AM

Thanks for the report. Many customers are running into the same issue with other controls. We are working on a fix for this problem for the final release. We are also considering releasing a patch for the RC build.

Posted by Microsoft on 2/17/2010 at 6:34 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you