Okay, but don't I need them for the editor to function?

  I'm not sure this is true if you use anything but the default compilation mode. If you want to pre-compile your asp.net 2.0 application to dll for deployment, I don't think it works. I keep getting build errors on all the CuteEditor client files and the build fails.

  Not to be too pushy, but is anyone looking at this issue? I was using it in a project and finding out it won't work in medium trust shared hosting environments came as a bit of a rude surprise, to say the least.   If I can't use it in shared hosting environments is it possible to get a refund on my developer's ...

  I'm finding that while the editor (v.5) works fine on my local development server, using it on my shared hosting account (meaning multiple sites per server, hence the need for asp.net 2.0 sites on it to run in medium trust), I get the following:   Operation could destabilize the runtime. Description: An unhandled exception ...

  It appears that the browser detection when using cuteeditor and safari doesn't work:   System.Web.HttpCapabilitiesBase.get_MajorVersion() CuteEditor.Editor.get_BrowserType()   Somewhere in there it returns a null string where it should not be null and crashes things.   I don't know if that's a cuteeditor thing or a ...

Sorry for the ''inject script filtered'' thing, I had tried to paste in the javascript block and that was filtered but then the forums won't let me edit my post. Edit notes are required, but no matter what you enter there, it throws an exception that too many parameters were entered for edit notes. Hmm.

In the CuteEditor_Files/Scripts folder, edit ''insert_table.aspx'' and change line 16 which is a javascript code declaring var editdoc and find ''border=1'' in that string and change it to ''border=0''.   Line 16:     Scroll over and find this:     And change it to:   <!-- Inject Script Filtered ...

Just for everyone else who had a similar question, I emailed support with this question and the response was that my impression was correct - developer licenses have no restrictions on domain or IP, or for distribution with your web application.   The ''single machine'' restriction on the developer license vs. the developer team is to ...

Just wanted to clarify that developer licenses are not tied to domain or machine names, correct? IOW, I can develop on my local development server and then transfer the application using CuteEditor to multiple production servers, web sites, or domain names without problems... is that correct?   The developer license states for use on ''one ...