New to Telerik UI for ASP.NET AJAX? Download free 30-day trial

Details on Installation Approaches

Telerik UI for ASP.NET AJAX enables you to install the suite components by using the MSI file, the ZIP library, or the Telerik NuGet feed.

This article provides additional information about each installation approach. For the step-by-step guides on getting up and running with the suite, refer to the following articles:

MSI Installation

When you download the Telerik UI for ASP.NET AJAX controls, the wizard for the MSI installation will by default install the Telerik UI for ASP.NET AJAX suite in the C:\Program Files\Progress\ folder for 32-bit machines or in the C:\Program Files (x86)\Progress\ folder for 64-bit machines.

During the MSI installation process, you need to take the following into consideration:

  • Prior to R3 2017, the default installation paths were C:\Program Files\Telerik\ and C:\Program Files (x86)\Telerik\ respectively.
  • The latest package that is available for download has all updates/HOTFIXES applied already and you don't need to update it further.
  • The MSI installation will not overwrite previous Telerik UI for ASP.NET AJAX installations unless the current installation is of the same version.

ZIP Installation

The downloaded ZIP file contains the following folders:

  • AdditionalLibraries—Contains the Telerik document processing libraries, which allow you to import and export content between different formats.

  • BinXX—Contains the Telerik controls assemblies (.dll files), where XX represents the version of the .NET framework against which the assemblies are built.

  • EditorDialogs—Contains the Editor dialog files.

  • ImageEditorDialogs—Contains the ImageEditor dialog files.

  • Live Demos—Contains the product Quick-Start Framework and examples and the Visual Studio solution file that opens them. You can start the samples directly from this folder by using the StartExamples.exe file.

  • Scripts—All controls that are part of the suite have their scripts embedded as web resources. However, if you need to modify a script or use it as an external, you can find it in this folder.

  • Skins—All controls that are part of the suite have their skins embedded as web resources. However, if you need to modify a skin or use it as an external one, you can find it in this folder.

  • TypeScriptDefinitions—Contains the TypeScript definitions for the Telerik UI for ASP.NET AJAX client-side objects.

  • (Hotfix)—A lighter version of the full installation and is faster to download because it doesn't contain the live demos. It is handy to use it when you manually upgrade the project to a later version or from a trial to a registered developer version.

    To use the file, give full permissions to the ASP.NET user (if you are using IIS5) or to the Network Service account (under IIS6, Windows Server 2003) for the folder where the files were extracted.

When using the ZIP installation approach, note the following:

  • If you are using a modified or external script, you need to set the EnableEmbeddedScripts property to false. Otherwise, the control will fail to load its client scripts with an exception. For more information, refer to the article on disabling embedded resources.

  • If you are using a custom or a modified skin, you need to set the EnableEmbeddedSkins property to false. Otherwise, the control will fail to find your custom skin with an exception. If you want to use a custom skin, it will override your CSS file. For more information, refer to the article on how skins work, how to register a skin, and how to disable embedded resources.

  • The latest package available for download has all the latest updates and HOTFIXES applied and you don't have to update it further.

To register the MS Help 2 files to Visual Studio and MSDN, refer to the article on adding help to Visual Studio

To add any control to the VS.NET toolbox, refer to the article on adding Telerik UI for ASP.NET AJAX to the Visual Studio toolbox.

To use any Telerik ASP.NET control in your project, refer to the article on adding Telerik UI for ASP.NET AJAX to an ASP.NET WebForm.

NuGet Installation

In addition to the steps for getting up and running with Telerik UI for ASP.NET AJAX by using the Telerik NuGet feed, the NuGet installation approach enables you to locally download a specific NuGet package and build a private NuGet feed for your company and also to implement continuous integration automated builds.

Downloading a NuGet Package

You can locally download .nupkg files and build a private feed for your company.

Such a feed must be private, that is, not available to the general Internet. Also, the developers working with the controls must have active licenses, that is, the standard developer-seat licensing model applies to that feed.

To download .nupkg files locally:

  1. Navigate to Your Account.

  2. Go to the Downloads tab of UI for ASP.NET AJAX.

  3. Click the .nupkg files you require to download them—for example, Telerik.UI.for.AspNet.Ajax.Net45.2022.1.119.nupkg. The file names follow the Telerik.UI.for.AspNet.Ajax.Net<.NET version of your project>.<Telerik controls version>.nupkg format.

  4. Configure your server and projects to use the feed.

Implementing Automated Builds

You may also want to set up Continuous Integration and/or Continuous Delivery (CI/CD) pipelines or builds for your project that uses the Telerik components. This is a valid scenario and the "one license per developer" license does not prevent you from doing so. The Telerik components are commercial software and as such can only be distributed through channels that are private and/or behind authentication.

To implement CI/CD automated builds, choose either of the following common approaches:

  • Restore the Telerik NuGet packages by downloading them from the Telerik NuGet server. You can achieve this by using the more secure token-based authentication with the Telerik NuGet server. If you prefer the basic authentication with a username and password, put your own credentials or the credentials of the license holder in the nuget.config of the build machine or pipeline. In this case, make sure that your credentials are encrypted when you add the Telerik feed source through the CLI. Alternatively, you can copy an encrypted version from your own local config if you have one and if plain text is an issue. For more information about adding credentials through the NuGet.config, refer to

  • Create a local folder on a shared network drive or other suitable location accessible by your builds and team. This folder will hold the provided .nupkg files, which you can download from your Telerik account.

You need to protect your credentials and ensure they are used only by you and not by other developers according to the license-per-developer policy. For example, take your encrypted password from your local NuGet.config file and use it on the build PC. They can be used by other developers, QAs, designers, front-end developers, DBAs, and so on, for building and running a solution provided they do not use the Telerik components to create functionalities. You have to ensure that such credentials or package sources are not available to the general public, for example, in public repositories.

See Also

In this article