Rich Finn

<update date="6/19/08">

Telerik has released the MOSS compatable version of the RadEditor that places all needed files as class resource files in the _wpresource directory.  They've also made some very nice improvements over the previous release that make extending and customizing the editor very easy.

</update>

Yesterday I posted about using the new RadControls for ASP.NET AJAX in MOSS, and I started moving the old controls in my current project over to the new ones.  Just now, I found a problem when I was converting the RadEditor from the old to the new.

In the Telerik online documentation for getting started with the RadEditor, they say that in a standard ASP.NET AJAX application, you need to utilize the App_GlobalResources and App_Data ASP.NET folders in order to use the RadEditor.

That's not any different for MOSS.

In the root of your SharePoint Web Application (\Inetpub\wwwroot\wss\VirtualDirectories\YourWebApp) create a folder named App_Data.  Drop in the RadSpell folder from the App_Data folder of the RadControls install directory (C:\Program Files\Telerik\RadControls for ASPNET AJAX Q1 2008).  Then, drop the RESX files from the App_GlobalResources directory located at the Telerik install root into the already present App_GlobalResources directory in your SharePoint Web Application root.

I think there's probably a better a way to do this using a Solution, but I'll worry about that later.  Not sure if we can deploy into those folders via a WSP - I don't think so.  I know there's a public property on the RadEditor that allows you to point to where the RadSpell directory is, but can't find anything for the RESX files.

Also, make sure you add the following line to the HttpHandlers section of your web config file, or else, spellcheck won't work:
<add verb="*" validate="false" path="Telerik.Web.UI.SpellCheckHandler.axd" type="Telerik.Web.UI.SpellCheckHandler, Telerik.Web.UI"/>

Anyway, here's a screen shot of the unskinned and unmodified RadEditor running in my local MOSS environment.  This is not tied into a publishing placeholder, but that's not what I'm using it for right now...