Thanks, yes that works - the problem arises when the control is dropped into a .ascx file, which is then rendered by our master .aspx page.
The 'register' tag ought to take care of the assembly reference i think, but we tried 'using' the class in the .ascx file as well just to be sure... no change.
The .ascx code-behind is below - note that we are using a custom UserControl class (which inherits 'System.Web.UI.UserControl') but there is nothing in it really other than a private StateBag.
public class TestCute : Admin_UserControl
{
protected CuteEditor.Editor Editor1;
private void Page_Load(object sender, System.EventArgs e)
{
// Put user code to initialize the page here
}
#region Web Form Designer generated code
override protected void OnInit(EventArgs e)
{
//
// CODEGEN: This call is required by the ASP.NET Web Form Designer.
//
InitializeComponent();
base.OnInit(e);
}
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
this.Load += new System.EventHandler(this.Page_Load);
}
#endregion
}
Any ideas?
Thanks,
Greg
P.S. couldn't find any control methods or properties that seemed to want to be in the Page_Load event and assumed that is correct since the text box renders.
G