Cannot embed standard asp.net controls in Ajax Control Toolkit TabContainer

Posted by Microsoft on 3/5/2010 at 2:21 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/27/2010 at 2:45 PM

This bug will be fixed in Visual Studio 2010 RTM.

In addition, we are working on releasing a batch for Visual Studio 2010 RC.

Posted by Martin.Robins on 2/19/2010 at 12:17 PM

This issue is also reported in bug 533945.

Posted by Martin.Robins on 2/19/2010 at 12:09 PM

Also the same issue in bug 533302.

Posted by Martin.Robins on 2/19/2010 at 12:02 PM

This is the same issue as is reported in bug 533071 - all of you who have upvoted this issue and/or confirmed that you can reproduce the problem please also add your weight to the related item so that it becomes clearer that we need it fixing. It is also worth noting that in bug 533071 it has been stated that this will not be resolved as any kind of hotfix but will have to wait until RTM (April/10?).

Posted by Martin.Robins on 2/19/2010 at 11:38 AM

I concur with Andrew111; I have just tried a simple asp:Wizard control and only the outer control is referenced in the .designer.cs file - all of the asp:WizardStep and enclosed controls (WizardStep1 & TestTextBox) are missing...

    <asp:Wizard ID="Wizard" runat="server">
        <WizardSteps>
            <asp:WizardStep ID="WizardStep1" runat="server">
                <asp:TextBox ID="TestTextBox" runat="server" />
            </asp:WizardStep>
        </WizardSteps>
    </asp:Wizard>

These controls are within the <ContentTemplate> of an asp:UpdatePanel. I have also tried placing the markup outside of the asp:UpdatePanel and it makes no difference - the controls are still missing in code-behind.

I can also confirm that I am trying this in a Web Application project targeting .NET Framework 4 but unlike Joe Washington I have not yet tried the same in a Web Site project.

Unfortunately, it does indeed look like Web Application project development is completely broken in the RC.

Posted by Joe Washington on 2/19/2010 at 12:16 AM

I also have the same issue. Its turns out that the problem is caused when using a Web Application rather than a website which is a huge bug.

Posted by Andrew111 on 2/18/2010 at 10:34 AM

Same with asp:Wizard

Posted by AaronDayalan on 2/17/2010 at 9:24 AM

so i think i mis-spoke earlier...

this maybe localized to the ajax toolkit.
case in point, an UpdatePanel's contentTemplate will be generated in the designer.

my suspicion is that the RC version of VS is working slightly differently in the way it interprets controls and generates the designer file. Maybe theres an attribute that needs to be set, or set differently in the ajax control toolkit's controls that implement an ITemplate.

I've started inspecting and comparing the code of the ajax toolkit's controls to the disassembled code of the .net UpdatePanel.

haven't gone to deep yet, but i think i'm on to something... we'll see.

Posted by Vs2010Dummy on 2/16/2010 at 1:45 PM

I have same problem with a control (button) inside of gridview (inside of updatepanel). will not generate
designer.vb correctly, is only ok for controls outside of gridview.

Posted by Vs2010Dummy on 2/16/2010 at 1:40 PM

Any control inside tabcontainer, will not be put into designer.vb either. was ok in beta 2.

Posted by AaronDayalan on 2/16/2010 at 12:07 PM

This is far worse than it seems.

Apparently anything using an ITemplate is invisible to VS when autogenerating the designer files.

ie: make a ListView, put a label in the itemtemplate... VS ignores it
or Accordion and its content template, or a repeater...

its all hosed.

Posted by Chris Powers on 2/11/2010 at 6:59 PM

I have encountered this issue as well. Anything placed inside a TabContainer is not represented within designer.cs files. Observed issue in both pages and user controls.

Posted by Martin.Robins on 2/11/2010 at 8:31 AM

Actually, to ammend my last comment, the controls can be added but do not always render correctly in the designer either.

Posted by Martin.Robins on 2/11/2010 at 8:23 AM

I too see this problem. I have also tried rebuilding the AjaxControlToolkit targeting .NET4 but this makes no difference.
The controls can be added in source view, and they will show up correctly in the design view and the properties window but though the control declarations remain in the markup, they are not added to the .designer.cs code-behind so you cannot access them from code behind.

Posted by Microsoft on 2/10/2010 at 11:13 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

Posted by Microsoft on 2/10/2010 at 7:05 PM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)

Posted by Martin.Robins on 2/11/2010 at 8:34 AM

If you create the controls using source view, and then add manually add the control declarations to your code-behind (not the .designer.cs) then you can continue to use the controls and they will render correctly in the browser.
Thing is, you lose the designer support.

Cannot embed standard asp.net controls in Ajax Control Toolkit TabContainer by Dennis Shen