This document describes assemblies required by web projects that use the functionality of the ASPxHtmlEditor control. Some of the assemblies are essential, while others that provide additional functionality can be optionally deployed, depending on your requirements.
We recommend you use our Assembly Deployment Tool, which allows you to automatically collect the required redistributable DevExpress (and custom) assemblies to deploy your application. Otherwise, you can deploy the required assemblies manually.
If you use other DevExpress components in your project, using and deploying them should comply with corresponding EULA documents. For more details on licensing information and the redistribution policy of DevExpress, refer to Redistribution and Deployment.
Depending upon the permissions you have on a production server and the amount of web applications that use the same assemblies provided by DevExpress, you can either register the assemblies in the global system 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 ASP.NET Deployment Content Map in MSDN.
Below are the essential libraries required by applications that use the ASPxHtmlEditor control. 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.
If ASPxHtmlEditor is integrated into the SharePoint environment, the following assemblies should be registered within the SharePoint server's GAC. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA. See Installation to learn more about DevExpress SharePoint solutions that automatically register required assemblies.