Roger,

 

I know what you need.

 

To get well-formed XHTML/HTML, CuteEditor have many processing steps. For CuteEditor for .NET, if you want to output well-formed XHTML, you need to use Editor.XHTML property. 

 

When you use Editor.XHTML property to extract the content, CuteEditor will have two steps to clean your code:

 

1. Client side clean up.

 

2. Server side clean up, convert HTML to XHTML

 

The reasons we convert HTML to XHTML in the server side are: a. Better performance. b. Better XHTML code.

 

For classic ASP, we don't have choice. We have to finish the step 2 in the client side as well.

 

When you call editor1.getHTML(), it's a JavaScript API. It always return HTML code instead of XHTML code.

 

>>"Is there a way to make sure the editor is always in XHTML mode so that when I call GetHTML() I am returned the HTML in an XHTML format?"

Not in the client side.

I know we can have a solution to write some code like we did for classic ASP. Put some converting works in the client side and allow the developer get code in XHTML formet. But for the whole project, we won't do that.  Because it will add some extra JavaScripts Code to CuteEditor for .NET. It will slow the loading speed.

Does it help?

Let me know if you have any further questions.