Which files and folders are mandatory to be on the server for RadControls to function

Search:

Browse:

My Favorites

RadControls for ASP.NET and ASP.NET AJAX

RadEditor MCMS Premium edition

RadEditor MCMS Lite Edition

RadControls for WinForms

RadControls for Silverlight 2

Open KB Article ID:

KB Article

Home

Support

Knowledge Base

Category

Which files and folders are mandatory to be on the server for RadControls to function

(ID#606) Which files and folders are mandatory to be on the server for RadControls to function

Rating:

Last Modified: 4/24/2008

Article information
Article relates to	RadControls all versions
Created by	Paul, Telerik
Last modified	February 20, 2008
Last modified by	Stephen, Telerik

QUESTION
Which files and folders are mandatory to be on the server for RadControls to function properly?

ANSWER

The answer to this question depends on your application's requirements. Some of the required files and folders will depend on your application's requirements (Skins, .NET2.x's Theming mechanism, etc.).

Here are some guidelines:

you will need the appropriate assembly in the bin folder of your application
in case you set UseEmbeddedScripts to false for the control or use predefined skin which differs from Default, you will need the appropriate RadControls/[control] folder for each control that you use - this folder contains all needed resources for the control to operate
you will need the App_Themes folder in order to use themes

.NET1

The files and folders which you can remove, depending on your application's requirements are:

the \RadControls\[control]\Intellisense folder, if you are not using Intellisense
the \RadControls\[control]\Skins\[skin] folders of the skins you do not need
the \RadControls\Editor\Localization\[language] folders of the languages you do not need
the \RadControls\Spell\Localization\[language] folders of the languages you do not need
the files in the \RadControls\Spell\TDF folder, which are not needed for your application
the themes' folders in the \app_themes folder, which are not used by the navigational controls
(for versions of RadControls before Q3 2006)
the \RadDesigner\CSharp(VB.NET)\Primavera folder
(for versions of RadControls before Q4 2005)

.NET2 and .NET3

Since Q2 2006, all resources (scripts, skins, images, etc) have been implemented as Embedded WebResources in most of our ASP.NET 2.0 versions of RadControls for ASP.NET. We did this for easier and faster deployment. The files which have been embedded are the Default control skin and its images, as well as the control's client scripts.

On the other hand, you have the option to disable the embedded scripts by setting UseEmbeddedScripts for the corresponding control to false. In this case you will need to copy the \RadControls\[control]\Scripts folder from the installation folder to the root of your web site/application.

The files and folders which you can remove, depending on your application's requirements:

A. RadEditor, RadSpell, and RadWindow

these controls do not follow the above rule of embedded resources - they use external files (localization files, dictionaries, ascx controls, etc.) which cannot be easily embedded. These controls should always have their respective RadControls\[control] folder in the application;
for efficiency purposes, you can delete all skins, EXCEPT the skin being used by the control;
remove the \RadControls\Editor\Localization\[language] folders of the languages you do not need
remove the \RadControls\Spell\Localization\[language] folders of the languages you do not need
remove the dictionaries in the \RadControls\Spell\TDF folder, which are not needed for your application

B. all other RadControls

if you are using the Default control skin (which is embedded in the assembly) or a custom skin of yours, you can remove the \RadControls\[control]\Skins\ folder, unless your custom skin uses any of the resources in it;
if you are using a Telerik skin, different from the default, you can safely remove all \RadControls\[control]\Skins\[skin] folders of the skins you do not need;
if you have not set UseEmbeddedScripts to false for the respective control, you can safely remove the \RadControls\[control]\Scripts folder because the client scripts will be referenced from the embedded resources

.NET2 and .NET3

By default all resources (scripts, skins, images, etc) have been implemented as Embedded WebResources in the ASP.NET 2.x/ASP.NET 3.x versions of RadControls for ASP.NET AJAX. We did this for easier and faster deployment. The files which have been embedded are 11 predefined skins and their images (for each control), as well as the controls' client scripts.

On the other hand, you have the option to disable the embedded scripts/skins by setting EnableEmbeddedScripts/EnableEmbeddedSkins for the corresponding control to false. In this case you will need to copy the \Scripts\[control] folder from the installation to the root of your web site/application.

RadEditor and RadSpell

these controls have several external resources which are mandatory for their proper usage - they use external files (dictionaries and localization files) which cannot be embedded. For RadSpell they should reside under the App_Data/RadSpell folder while if you use localization for RadEditor you will need to copy the localization file in the App_GlobalResources folder.

For all RadControls

If you have not set EnableEmbeddedScripts to false for the respective control, you can safely remove the \Scripts\[control] folder because the client scripts will be referenced from the embedded resources.
In case you set EnableEmbeddedSkins to false for the respective control, you are free to customize the appearance of the control in par with your preferences and specify paths to your custom css styles/images.

Article Comments

WaldenL, 5/31/2007
But should be more simple to find. This is needed by everyone that deploys.

richardlennox, 6/8/2007
AS with a lot of your documentation, this has a lot of gaps. for instance where is the default location of the \radcontrols folder after installation? I think you should look carefully at your knowledge books and who they are catered for.

N8WEI, 6/8/2007
Telerik should provide a deployment tool or project configuration tool, which handles the process of making sure the appropriate resources are in the project. This tool should allow the user to specify which skins they are using for each control (or a global skin) and only copy the skins being used into the RadControls folder (or not if they are using the default), etc. If this was implemented as an add-in to VisualStudio, that added an option to the context menu for the web project. (i.e. right-click... Configure Telerik controls) then if things changed from version to version, simply updating to the next version of the controls would result in a new version of the configuration tool, which may have changes of its own. Just an idea..

Telerik Admin, 6/14/2007
The default location for the /RadControls folder after the installation is completed C:\Program Files\telerik\[ControlName_and_Version]\NET1\RadControls or C:\Program Files\telerik\[ControlName_and_Version]\NET2\RadControls. We will continue improving our installation documentation for the next versions of the products - thank you for your feedback.

Art, 10/12/2007
Why can't you be more explicit about exactly what needs to e copied into what folders? In the tutorial, I see something about copying the input folder but I don't see the same files in my installation folder. Could you PLEASE explain what needs to be copied and how it needs to be added via Visual Studio?

Telerik Admin, 10/15/2007
Consider reviewing the topics from the documentation residing in the Installation and Deployment -> Installation section, for example for RadInput: http://www.telerik.com/help/aspnet/input/. They contain all the necessary information about the files and folders required by our controls to function properly.

Please Sign In to rate this article or to add it to your favorites.

Print Send to a friend