EricHarlan

Installing Telerik RadControls and Rad Editor into SharePoint 2007

I needed to install some third party software for a client. In addition to a few others the Telerik Rad controls were among them. I went through their process a few times on my virtual image and for some reason or another, I never had much luck, either something didn’t register correctly or I did something incorrectly.  I tried some other methods of getting Ajax up and running in my environment including the codeplex solution. This didn’t work for me either.  With a tight deadline I just figured it out.

So if you’re trying to install the Telerik RadControls or Rad editor here’s what I did to get there, step by step.  This is kind of a hybrid between a few different methods i’ve found online. Some taken from Telerik’s website, but not all. Its the order that got me the results.

Enjoy.

NOTE: All processes must be followed exactly as listed. It is important to take one’s time to do this correctly the first time.
Prerequisites

Prerequisites for Telerik controls to work:
1.    .Net 3.5 SP1 needs to be installed on all the Web Front End (WFE) servers
2.    Ajax 1.0 allowed in all WFE web.config files
3.    ScriptManager references in master pages
4.    Editor deployed as a feature.
5.    Populate web part gallery and use Rad Editor
Step 1 .Net 3.5 SP1

Install .Net 3.5 SP1 from this link http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en

Step 2 Ajax configuration

After ASP.NET 3.5 has been installed you need to modify the web.config file of your MOSS web site with a few Ajax specific entries. Typically, the web.config file is located in c:\inetpub\wwwroot\wss\virtualdirectories\80
1)Add the following element in the tag:

type=”System.Web.Configuration.SystemWebExtensionsSectionGroup,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″>

type=”System.Web.Configuration.ScriptingSectionGroup,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″>

allowDefinition=”MachineToApplication”/>

allowDefinition=”Everywhere” />

type=”System.Web.Configuration.ScriptingProfileServiceSection,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″ requirePermission=”false”
allowDefinition=”MachineToApplication” />

allowDefinition=”MachineToApplication” />

type=”System.Web.Configuration.ScriptingRoleServiceSection,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″ requirePermission=”false”
allowDefinition=”MachineToApplication” />

2) Add the following section as a child of the / tag:

3) Add the following tag to the tag, within the element:

4) Register the following HTTP handlers at the end of the  section:

type=”System.Web.Script.Services.ScriptHandlerFactory,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

type=”System.Web.Script.Services.ScriptHandlerFactory,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

type=”System.Web.Handlers.ScriptResourceHandler,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″ validate=”false”/>

5) Add the following HTTP module registration to the section beneath any existing modules:

type=”System.Web.Handlers.ScriptModule,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

6) Add a SafeControl entry for the System.Web.UI namespace from the System.Web.Extensions assembly within the / section:

Namespace=”System.Web.UI” TypeName=”*” Safe=”True” />

7) Since the RadEditor dll files, which are in the wsp package, are complied for .NET 2.0 framework, you need to add the following code to the section.

8) Finally, add the following configuration tags at the bottom of web.config, just before the end of the tag:

type=”System.Web.Handlers.ScriptModule,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

preCondition=”integratedMode”
type=”System.Web.Script.Services.ScriptHandlerFactory,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

path=”*_AppService.axd”
preCondition=”integratedMode”
type=”System.Web.Script.Services.ScriptHandlerFactory,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″/>

verb=”GET,HEAD” path=”ScriptResource.axd”
type=”System.Web.Handlers.ScriptResourceHandler,
System.Web.Extensions, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35″ />

Step 3 Incorporating RadControls for ASP.Net Ajax in MOSS
Once all steps from the previous articles have been performed, you can easily integrate RadControls for ASP.NET Ajax in your MOSS site.

1) Launch Office SharePoint designer and open the desired SharePoint site

2) Within the Folder List tool window expand the tree until the master pages folder is visible. A typical location is http://server_name/_catalogs/masterpage

 

3) Open the master page currently used by your site (e.g. default.master). If prompted to check out the file select “Yes”.

4) Since RadMenu is ASP.NET Ajax control, it requires a ScriptManager control to be present on the page. Add the following markup just after the beginning of the tag:


Step 4) Deploying RadControls for ASP.NET Ajax

To leverage RadControls for ASP.NET Ajax, some required files must be deployed to each SharePoint Web Front End (WFE) server. This section outlines the required steps that need to be taken to deploy RadControls for ASP.NET AJAX prior to implementing it within an existing MOSS web site.
1) First you need to install Telerik.Web.UI.dll in the GAC (Global Assembly Cache) of your SharePoint server. There are two ways to do this:

2) Drag and drop Telerik.Web.UI.dll into C:\Windows\Assembly (in Windows Explorer)

3) Next you should tell SharePoint that the controls from the Telerik.Web.UI.dll (and Telerik.Web.Design.dll) are safe to use. To do so you should add a few entries within the section in your web.config:

Step 5 Deploying Rad Editor Web Part

1) Extract the contents of RadEditorMOSS_5_1_1.zip

2) Open a command prompt window.

3) Run the stsadm.exe utility to install RadEditorMOSS solution.
By default stsadm.exe can be found in [Program Files]\Common Files\Microsoft Shared\web server extensions\12\BIN.
Use the following syntax:
stsadm -o addsolution -filename [Path]\RadEditorMOSS.wsp

4) Open the SharePoint Central Administration site

5) Go to the Operations page and click on Solution Management.

6) You should see the radeditormoss.wsp solution in the list. Click on the name link to go to the Solution Properties page.

7) Select Deploy Solution.

8) From the next page you can choose when and to which applications to deploy the solution.

9) After a successful deployment you will see the following screen:

Note: If you see the following exception – “Request for permission of type…” when you try to open a page containing the editor, then you might need to modify the web.config of your SharePoint application and set the Trust level to at least Medium level. This can happen if you choose to deploy the editor solution to a single site (in the BIN folder) instead of to all sites (in the GAC).

Step 6 Using the web part

1) Navigate to your SharePoint site and login as the administrator

2) Navigate to the site settings and select “Web Parts”

3) Select “New” in the web part Gallery

4) Scroll to the bottom of the page and check the box next to “Telerik.SharePoint.RadEditorWebPart”

5) Once checked, scroll back up and hit the “Populate Gallery” button

6) Go back to the page you want to add the RadEditor to. Select Site Actions > Edit Page

7) Select the Telerik RadEditor for Moss Web part and hit the “add” button.

8) The web part is now on the page, hit “edit” and edit the content you want into the web part. In order for the changes to take effect you must hit “OK” or “Apply” in the Web Part properties pane. You not simply hit publish.

Tagged on:

Leave a Reply

Your email address will not be published.

No seriously, are you human? *