The reply that I had received was that there was problems to be fixed in a later release.
I however managed to get 90% of my controls (even some custom controls) working although viewstate on drop downs is not functioning as expected. I also rebind most if my controls each postback.
Here is a brief summary of what you probably need to know.
Using a template class created the desired layout of your controls. This template class is created passing in a reference to the parent or calling control that contains the NavBar component.
/// <summary>
/// My template class
/// </summary>
public class DocumentationTemplate:ITemplate
{
// The parent control that contains the nav bar control
private ControlInputControl m_parentControl;
/// <summary>
/// Simple constructor
/// </summary>
/// <param name="_parentControl"></param>
public DocumentationTemplate(ControlInputControl _parentControl)
{
m_parentControl = _parentControl;
}
/// <summary>
/// Where all the layout and controls are kept
/// </summary>
/// <param name="container"></param>
public void InstantiateIn(System.Web.UI.Control container)
{
// Create your controls in the parent class and then reference them in here.
// i.e
Row = new TableRow();
Cell = new TableCell();
Cell.Attributes.Add("Width", "80%");
Cell.Controls.Add(m_parentControl.myDropDownList);
}
Then in the CreateChildControls of the main control containing the NavBar component I do the construction of the DropDown List control (and all other controls that I am using.
The control in my case is created as a member variable of this c
i.e.
protected override void CreateChildControls()
{
try
{
myDropDownList = new DropDownList();
myDropDownList.CssClass = "ControlDropDown";
myDropDownList.AutoPostBack = true;
// etc etc
The event handling function is then handled in the parent class rather than the Template class.
I hoep this helps a little. Please post if it does not.....
Regards