Edit this page

Included Assemblies

This article explains what assemblies are included in the Telerik® UI for ASP.NET Ajax installation: the main Telerik.Web.UI assemblies, the Telerik ZIP library and the Telerik Document processing libraries (text processing and spreadsheet processing). You can find more information about them in the sections below.

The assemblies come sorted in several folders so that you can use the appropriate ones. Depending on the .NET framework version your project targets, you will find the needed assemblies in the corresponding directory:

  • If you target .NET 3.5, you must use the assemblies from the Bin35 folder.
  • If you target .NET 4.0, you will need the assemblies from the Bin40 folder.
  • If you target .NET 4.5, .NET 4.6 or .NET 4.7, you should use the assemblies from the Bin45 folder.

The binaries from the Additional Assemblies folder may have different versions than the main assemblies. You must use the assemblies from the same release as the main assemblies.

Main Assemblies

The Telerik® UI for ASP.NET Ajax product consists of the assemblies in the list below. You can find them in the root of the installation (both automated and in the zip archive) and in the internal builds archives.

  • Telerik.Web.UI.dll—(required)—the core assembly from the suite where the actual controls are located. It also contains the Default skin.

  • Telerik.Web.UI.Skins.dll—(optional)—this assembly has all the skins the suite offers except the Default one.If you use only the Default skin, or you only use custom skins, you do not need this assembly.

  • Telerik.Web.Design.dll—(optional)—this assembly contains the Visual Studio Design surface code for the suite. The configuration wizards you can access from the controls' Smart Tags are also there. It is only needed if you use the controls in the Design mode in VS and is not needed in the deployed application. The automated installation adds this assembly to the GAC.

  • Telerik.Web.Device.Detection.dll—(optional)—the Telerik Device Detection framework that can help you determine, with a few lines of code, the screen resolution of the device that requested the page while processing the request on the server. It is used by the Telerik controls to determine the RenderMode when it is set to Auto. If you use only the Classic, Lightweight or Mobile Render Mode (no mentions of the Auto mode), you do not need this assembly.

Telerik ZIP Library

This is a cross-platform library that lets you load, create and update Zip archives on the fly with easy to use API.

You can find its assembly in the AdditionalLibraries folder in the Telerik® UI for ASP.NET Ajax installation (automated and manual) and in the internal builds archive. It supports .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the assembly from the Bin40 or Bin45 folder respectively.

  • Telerik.Windows.Zip.dll—the assembly of the Telerik Zip Library.

  • Telerik.Windows.Zip.Extensions.dll—extends Telerik.Windows.Zip assembly with aditional helper methods (Zip Extensions).

You can read more about it in its documentation: Getting started with RadZipLibrary.

Telerik Spreadsheet Library

The Telerik.Web.Spreadsheet.dll library is an assembly that lets you use the RadSpreadsheet control in your project. You will also need the Newtsoft.Json.dll assembly.

You can find the needed assemblies in the AdditionalLibraries folder in the Telerik® UI for ASP.NET Ajax installation (automated and manual) and in the internal builds archive. They support .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the assemblies from the Bin40 or Bin45 folder respectively.

For more information about the usage of the RadSpreadsheet see its Getting Started article.

Telerik Document Processing Libraries

The Telerik document processing libraries are a set of assemblies that let you import and export content between different formats.

You can find the needed assemblies in the AdditionalLibraries folder in the Telerik® UI for ASP.NET Ajax installation (automated and manual) and in the internal builds archive. They support .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the assemblies from the Bin40 or Bin45 folder respectively.

  • Telerik.Windows.Documents.Core.dll—the main assembly from the Telerik document processing libraries. You always need it when you intend to use the library.

  • Telerik.Windows.Documents.Flow.dll—part of the words (text) processing library. It is needed for processing HTML, DOCX, RTF and TXT documents.

  • Telerik.Windows.Zip.dll—needed for working with zipped formats (DOCX, XLSX) and PDF.

  • Telerik.Windows.Documents.Flow.FormatProviders.Pdf—allows exporting of flow documents (DOCX, RTF) to PDF.

  • Telerik.Documents.SpreadsheetStreaming.dll—The main assembly for generating huge spreadsheet files using minimum resources.

  • Telerik.Windows.Documents.Spreadsheet.dll—the main assembly for the spreadsheet processing. It is needed for processing XLSX, CSV, TXT documents.

  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.dll—allows import/export of spreadsheet document model from/to XLSX.

  • Telerik.Windows.Documents.Fixed.dll—this assembly is needed for processing PDF documents.

  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.dll—allows exporting of spreadsheets (XLSX, CSV) to PDF.

You can find more information on working with the Telerik document processing libraries in the following articles:

Newtonsoft.Json.dll

The Newtsoft.Json.dll assembly is located in the AdditionalAssemblies folder and you need to deploy it when you use the RadCloudUpload control, the RadScheduler WebAPI binding or the RadSpreadSheet control.

If your project references a different version of this assembly, review the Newtonsoft.Json is Built by a Higher Version Than the Currently Targeted Framework section for more information.

See Also