Deployment of ASPxGaugeControl
- 3 minutes to read
This document describes assemblies required by web projects that use the functionality of the DevExpress ASP.NET Gauges. Some of the assemblies are essential, while others that provide additional functionality can be optionally deployed, depending on your requirements.
Note
If you use other DevExpress components in your project, their use and deployment should comply with the corresponding EULA documents. For more information on licensing and the DevExpress redistribution policy, refer to the following topic: Redistribution and Deployment.
Depending upon the production server’s permission settings and the number of web applications that use the same DevExpress assemblies, you can either register the assemblies in the Global Assembly Cache (GAC) or place them into your application’s Bin folder on the target computer. See the following topic to learn more about web project deployment techniques: ASP.NET Deployment Content Map.
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 are the essential libraries required by applications that use the DevExpress ASP.NET Gauges. These libraries are considered to be redistributable under the .NET Controls & Frameworks EULA, and thus can be redistributed legally.
Assembly | Description |
---|---|
DevExpress.Data.v24.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.v24.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. |
DevExpress.Printing.v24.2.Core.dll | Contains classes that implement the basic functionality for DevExpress printing libraries. |
DevExpress.RichEdit.v24.2.Core.dll | Contains a public API to format and modify rich text documents. This API is common to such DevExpress RTF controls as ASP.NET RichEdit, WinForms RichEdit, and WPF RichEdit. This assembly is also required when you use a Rich Edit in-place editor (RepositoryItemRichTextEdit) and/or export data to DOCX. |
DevExpress.XtraGauges.v24.2.Core.dll | Contains common algorithms for drawing gauges in different platforms for XtraGauges and ASPxGauges. |
DevExpress.XtraGauges.v24.2.Presets.dll | Contains over 150 ready-to-use Gauge presets for the ASPxGauges and XtraGauges Suites. |
DevExpress.Web.ASPxGauges.v24.2.dll | Contains classes that implement functionality related to the ASP.NET Gauges. |
Optional Libraries
The following libraries provide additional functionality for web projects that use the functionality of the DevExpress ASP.NET Gauges.
DevExpress Themes
The following assembly should also be deployed if any DevExpress Theme is used.
Assembly
Description
DevExpress.Web.ASPxThemes.v24.2.dll
Contains classes that implement a set of predefined DevExpress Themes for DevExpress web controls. See the following help topic to learn more: ASPxThemes Assembly.
Redistributable Libraries
The following list summarizes libraries considered redistributable under the .NET Controls & Frameworks EULA:
- DevExpress.Data.v24.2.dll
- DevExpress.Web.ASPxGauges.v24.2.dll
- DevExpress.Web.ASPxThemes.v24.2.dll
- DevExpress.Web.v24.2.dll
- DevExpress.XtraGauges.v24.2.Core.dll
- DevExpress.XtraGauges.v24.2.Presets.dll
Note
All required DevExpress assemblies are located in the “C:\Program Files\DevExpress 24.2\Components\Bin\Framework\“ folder of your development machine after installation.
Non-Redistributable Libraries
The distribution of any DevExpress design-time libraries ending with “.Design” is strictly prohibited. This means that you cannot use our installation for deployment purposes because 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.