The Accordion extender, and probably any other Ajax Toolkit control which supposedly supports DataBinding only does so if the DataSource (ObjectDataSource, SqlDataSource, etc.) resides as a sibling element within the Html of the Page (i.e. within the same NamingContainer). However, if the DataSource control is within say a Parent NamingContainer, the DataSource is not found and an Exception is thrown from the control extender. This is not consistent with all other ASP.NET Controls and needs to be fixed. A DataBound control can be bound to any DataSource control that resides within the current NamingContainer or any Parent NamingContainer.
The method within Accordion.cs "ConnectToDataSourceView()" is incorrect. Please use Reflector to decompile the "System.Web.UI.WebControls.DataBoundControlHelper" class which will show you how to properly find the DataSource control from a specified DataSourceID.
To reproduce this, just add a ObjectDataSourceControl at the root of the Page heirarchy and then add an Accordion control with it's DataSourceID set to that control. Make sure that the Accordion control is nested within another server control such as a FormView or something (maybe even nesting it with Table tags will work).
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.
The method within Accordion.cs "ConnectToDataSourceView()" is incorrect. Please use Reflector to decompile the "System.Web.UI.WebControls.DataBoundControlHelper" class which will show you how to properly find the DataSource control from a specified DataSourceID.
To reproduce this, just add a ObjectDataSourceControl at the root of the Page heirarchy and then add an Accordion control with it's DataSourceID set to that control. Make sure that the Accordion control is nested within another server control such as a FormView or something (maybe even nesting it with Table tags will work).
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.