Skip to main content

Deployment of ASPxRichEdit

  • 4 minutes to read

This document describes the assemblies required by web projects that use the functionality of the DevExpress Rich Text Editor for ASP.NET. Some of the assemblies are essential, while others, which provide additional functionality, can optionally be deployed, depending on your requirements.


If you use other DevExpress components in your project, their use and deployment should comply with the corresponding EULA documents. For more details on licensing and the redistribution policy of DevExpress, refer to Redistribution and Deployment.

Depending on the permissions you have set on a production server and the amount of web applications that use assemblies provided by DevExpress, you can either register the assemblies in the Global Assembly Cache (GAC) or place them into the Bin folder of your application on the target computer. To learn more about web project deployment techniques, see the Web Deployment Content Map for Visual Studio and ASP.NET article.

Use our Assembly Deployment Tool to collect the required redistributable DevExpress and custom assemblies automatically to deploy your application. Otherwise, you can deploy the required assemblies manually.

Required Libraries

Below is a list of essential libraries required by applications that use the ASPxRichEdit. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA, and thus can be redistributed legally.




Implements the most basic functionality common to all DevExpress controls. This includes classes for data binding, skinning, printing, exporting, as well as many other auxiliary types and resources.


Contains classes that implement the basic functionality for DevExpress printing libraries.


Contains base classes common for Office File API and Office controls.


Contains classes that implement the logic for formatting rich text, as well as basic types that provide a public API common to such DevExpress RTF controls as ASP.NET RichEdit, WinForms RichEdit, and WPF RichEdit.

This assembly is also required when using a Rich Edit in-place editor (RepositoryItemRichTextEdit) and/or exporting to DOCX.


Contains classes that implement the core functionality of all DevExpress web controls and the functionality of controls from the following components: Data Editors, GridView, Card View, Vertical Grid, Data and Image Navigation, Docking and Popups, Site Navigation and Layout, File Management and Multi-Use Site Controls.


Contains classes that implement a functionality related to the ASPxRichEdit control. See ASPxRichEdit and DevExpress.Web.ASPxRichEdit to learn more.

Optional Libraries

The following libraries provide additional functionality for web projects that use the functionality of the DevExpress Rich Text Editor for ASP.NET. All of them are considered redistributable under the DevExpress EULA, and thus can be redistributed legally.

Redistributable Libraries

The following list summarizes the libraries considered redistributable under the DevExpress EULA.

  • DevExpress.Data.v23.1.dll
  • DevExpress.Printing.v23.1.Core.dll
  • DevExpress.Office.v23.1.Core.dll
  • DevExpress.RichEdit.v23.1.Core.dll
  • DevExpress.Web.v23.1.dll
  • DevExpress.Web.ASPxRichEdit.v23.1.dll
  • DevExpress.Web.ASPxThemes.v23.1.dll

This also includes the following resource assemblies for German (de), Spanish (es), and Japan (ja) languages.

  • DevExpress.Data.v23.1.resources.dll
  • DevExpress.Printing.v23.1.Core.resources.dll
  • DevExpress.Office.v23.1.Core.resources.dll
  • DevExpress.RichEdit.v23.1.Core.resources.dll
  • DevExpress.Web.v23.1.resources.dll
  • DevExpress.Web.ASPxRichEdit.v23.1.resources.dll



By default, all required DevExpress assemblies are located in the “C:\Program Files\DevExpress 23.1\Components\Bin\Framework\“ folder of your development machine after installation.

Non-Redistributable Libraries

Distributing any DevExpress design-time libraries ending in “.Design” is strictly prohibited. This means that you cannot use the DevExpress installation for deployment purposes, since it includes design libraries that cannot be distributed according to the terms of the EULA.


Please consult the EULA for additional up-to-the-minute information on which libraries, tools and executables are considered redistributable.