- 4 minutes to read
This document describes assemblies required by web projects that use ASPxCardView functionality. Some assemblies are essential, while others that provide additional functionality can optionally be deployed - based on your requirements.
If you use other DevExpress components in your project, their usage and deployment should comply with our corresponding End User License Agreements (EULA). For more details on DevExpress licensing and redistribution policies, refer to the following help topic: Redistribution and Deployment.
Depending on the production server's permission settings and the number of web applications that use the same DevExpress assemblies, you can either register those assemblies in the Global Assembly Cache (GAC) or place them in the application's Bin folder on the target machine. To learn more about web project deployment techniques, see the following MSDN article: ASP.NET Deployment Content Map.
The following essential libraries are required by applications that use ASPxCardView. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA, and can thus be redistributed legally.
|DevExpress.Data.v20.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.v20.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 ASPxCardView functionality. Some libraries 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 also need to 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. To see a detailed list of assemblies, refer to the following help topic: XtraPrinting - Deployment.
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. Deployment of these libraries requires a separate valid license for the eXpress Persistent Objects product.
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.
Use in SharePoint
If the grid is integrated into the SharePoint environment, the following assemblies should be registered within the SharePoint server's GAC. See the following help topic to learn more about DevExpress SharePoint solutions that automatically register the required assemblies: Installation.
Contains classes that implement integration of ASPxGridView and ASPxHtmlEditor into the SharePoint 2013 environment. See the following help topics to learn more: ASPxGridView - Support for SharePoint and ASPxHtmlEditor - Support for SharePoint.
If you use satellite resource assemblies to localize ASPxGridView, you need to deploy the corresponding assemblies. To learn more, see the following help topic: Localizing ASP.NET Controls via Satellite Resource Assemblies.
The following libraries are considered redistributable under the .NET Controls & Frameworks EULA.
By default, all required DevExpress assemblies are located in the "C:\Program Files (x86)\DevExpress 20.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 deployment purposes, 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.