Please open your VS solution.   Click the reference and remove the CuteEditor.dll refrence from your project.   Then add the reference of the new CuteEditor.dll to your project.    

You can still use the existing license file.   Just update the CuteEditor.dll and all the CuteEditor client files.    

Hi Adam, I purchased the upgrade and unzipped the files into a new folder. I am currently running CuteEditor 3 What suggestions do you have for upgrading to version 4. I am using a SQL server database to store and retrieve the html content.

I am licensed for version 1.0 of uploader but have tested this with verson 2.0 (trial) also in UploadType modes Flash and IFrame.  Both versions exhibit the same issue. Will a fix be provided in v1.0 as well as v2.0 or will I have to pay for an upgrade from v1.0 to v2.0 in order to receive a fix?

igloo,   I suggest you upgrade to the latest version. It's a free upgrade.   If you cannot upgrade to new version, we have to create a customized version for you.  Please write to karen@cutesoft.net with all detailed requirements.

This issue is resolved in the version 6.0. Please upgrade to this new version.   It's a free upgrade.   Demo:   http://richtextbox.com/cs/   Download: http://cutesoft.net/downloads/default.aspx  

noguan,   In version 3.1, we disable the online toolbar for embed messenger. I think you can enable it by modifying the xml UI file. But I suggest you just upgrade to verdsion 4.0. We improved a lot in version 4.0.  I will post the code and show you how to enable it later.    

Hi SaferSephy, If the online demo works for you, please download the latest version and try again.  latest version downloads http://cutesoft.net/downloads/folders/21904/download.aspx The upgrade is free. Regards, Ken

1. If you upgrade from an earlier version, delete CuteSoft_Client\CuteEditor\web.config file.   2. If your IIS is using Gzip, please add the following entry to web.config file:   <add key=''CuteEditorEnableGZip'' value=''False'' /> 

frJericho,   It fixed an uploader issue under firefox 3.6.4 + silverlight 3.   If clients upgrade silverlight to 4.0, this issue will go away.   If clients upgrade firefox to 3.6.6, this issue will go away too.