greetings - we are evaluating version 6.0 of the editor and have followed the deployment instructions. We are using VS 2003. The component drags into our aspx page fine and the app compiles under Debug however the CE Editor control is rendered as a plain text box.

I suspected  something to do with config files and so included the 'FilesPath' element in the web.config file. Once we got the path right it stopped complaining but no luck with the rendering problem.+

The Configuration Path property is blank. We tried entering a path there and got a runtime error (another story) and the documentations zseems to indicate that it is only needed if a custom config is to be used.

Anyone have any ideas?

TIA
Greg

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

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

Just to follow up - we got it to work, looks like it was an issue with VS debug and WebCache - apologies for any time you spent on it!