- 4 min to read
This document describes assemblies required by web projects, which use the functionality of the ASPxGridView control. Some assemblies are essential, while others (that provide additional functionality) can be optionally deployed, depending on your requirements
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 on the permissions you have on a production server and the amount of web applications that use the same DevExpress assemblies, you can either register those 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 ASPxGridView. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA, and can thus be redistributed legally.
|DevExpress.Data.v19.2.dll||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.|
|DevExpress.Web.v19.2.dll||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.|
The following libraries provide additional functionality for web projects that use the functionality of the ASPxGridView. Some of them are considered to be redistributable under the .NET Controls & Frameworks EULA, and can thus be redistributed legally, while others require separate licenses.
If the grid's export functionality is used (via the ASPxGridViewExporter), you need to additionally deploy the following assemblies. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA.
Assembly Description Assemblies required by the Printing-Exporting library. See the XtraPrinting - Deployment topic for a detail list.
Data Binding via XpoDataSource
If the grid is bound to an XpoDataSource, the following assemblies are required. Note: These libraries are not considered to be redistributable under the .NET Controls & Frameworks EULA. Deploying them requires a separate valid license for the product eXpress Persistent Objects.
Contains the classes that support the main functionality of the eXpress Persistent Objects Library.
Note: This assembly is also required when using XtraGrid's Server Mode.
Using in SharePoint
If the grid is integrated into SharePoint environment, the following assemblies should be registered within the SharePoint server's GAC. See Installation to learn more about DevExpress SharePoint solutions that automatically register required assemblies.
Contains classes that implement integration of ASPxGridView and ASPxHtmlEditor into the SharePoint 2013 environment. See ASPxGridView - Support for SharePoint and ASPxHtmlEditor - Support for SharePoint to learn more.
If you localize ASPxGridView using the satellite resource assemblies, you need to deploy the corresponding assemblies. To learn more, see the Localizing ASP.NET Controls via Satellite Resource Assemblies topic.
The following list summarizes the libraries that are considered redistributable under the .NET Controls & Frameworks EULA.
By default, all required DevExpress assemblies are located in the "C:\Program Files (x86)\DevExpress 19.2\Components\Bin\Framework\" folder of your development machine after installation.
Distributing any DevExpress design-time libraries ending with ".Design" is strictly prohibited. It means that you cannot use our installation for a deployment purpose since it includes design libraries that cannot be distributed according to the terms of our EULA.
Please consult the EULA for additional up-to-the-minute information on which libraries, tools and executables are considered redistributable.