Deployment
Deployment Steps
There are two main steps to follow when deploying an application that uses Actipro control products.
Configure Licensing
Please read the Licensing topic for details on the two options for applying purchased licenses. Once configured properly, your license data will either be applied via code or embedded into your application by the build process.
Include Redistributable Assemblies
Next, simply copy the appropriate redistributable assemblies to the same folder as your application's executable on the target machine. Nothing else needs to be deployed.
This table describes where referenced assemblies appear after project compilation:
| Reference Kind | Description |
|---|---|
| NuGet package reference | The referenced assemblies will be in your bin folder after compilation. |
| Assembly reference | The referenced assemblies will be in your bin folder after compilation if the "Copy Local" property on the reference (via the Visual Studio Properties window) is set to true. |
Redistributable Files
When you own a license for WPF Studio (our large control bundle), WPF Essentials (our smaller control bundle), or one of their individual products, you are licensed to redistribute certain files with your application.
The tables below show the product assemblies that may be redistributed based on the product(s) for which you own licenses.
Individual Products
This table shows the product assemblies that may be redistributed based on individual products for which you own licenses, and includes their source NuGet packages:
| Actipro Product | Redistributable Assemblies and Related NuGet Packages |
|---|---|
| Bar Code |
|
| Bars |
Optional companion to the Bars product that supports easy MVVM integration is also licensed:
|
| Charts |
|
| Docking/MDI |
|
| Editors |
Optional interop with PropertyGrid if Grids is also licensed:
Optional interop with the Microsoft DataGrid:
|
| Gauge |
|
| Grids |
|
| Micro Charts |
|
| Navigation |
|
| Ribbon |
|
| Shell |
|
| SyntaxEditor |
|
|
SyntaxEditor .NET Languages Add-on * |
|
|
SyntaxEditor Python Language Add-on * |
|
|
SyntaxEditor Web Languages Add-on * |
|
| Views |
|
| Wizard |
|
* Add-ons marked with an asterisk are sold separately from SyntaxEditor and its containing bundles. See this documentation for more details on licensing these add-ons.
Bundles
This table shows the two bundles that allow groups of Actipro control products to be licensed at a large discount:
| Actipro Bundle | Description |
|---|---|
| WPF Studio |
Available via the
|
| WPF Essentials |
Includes these products:
|
Others
There are several other optional assemblies that can be redistributed, some of which don't have NuGet packages available.
Legacy assemblies contain old deprecated code that is intended for backwards compatibility only. It is encouraged to not use these assemblies and switch to the current assemblies listed in the table above instead.
| Name | Description |
|---|---|
| Aero Themes |
Includes optional Windows 7 and Office 2010-like Aero themes. Not needed unless those older themes are required for your application. Licensed for all licensed customers.
|
| DataGrid Contrib |
Optional additional features and themes for the Microsoft WPF DataGrid. Open source and licensed for all licensed customers.
|
| SyntaxEditor ANTLR Integration |
Optional integration of SyntaxEditor with ANTLR v3 parsers. Licensed for customers who have licensed SyntaxEditor individually or via a bundle.
|
| SyntaxEditor Irony Integration |
Optional integration of SyntaxEditor with Irony parsers. Licensed for customers who have licensed SyntaxEditor individually or via a bundle.
|
| Legacy |
Several deprecated common controls, licensed for all licensed customers.
|
| Editors (Legacy) |
Licensed for customers who have licensed Editors individually or via a bundle, as these contain the old Editors codebase prior to the 2017.1 version.
|
| PropertyGrid (Legacy) |
Licensed for customers who have licensed PropertyGrid (predecessor to Grids) individually or via a bundle, as these contain the old PropertyGrid codebase prior to the 2017.1 version.
|
Default Assembly Install Folders
When the WPF Controls installer is run on a machine, .NET Framework redistributable assemblies are all installed to this folder by default:
<Drive>:\Program Files (x86)\Actipro Software\WPF-Controls\<Version>\Assemblies\
Note that .NET and .NET Core assemblies are not included in the WPF Controls installer. The .NET and .NET Core assemblies are available in the NuGet packages. The .NET Framework assemblies are contained in the NuGet packages as well.
Other Deployment Notes
No Run-time Royalties
There are no run-time royalties or other distribution charges for our WPF control products. We only require that you have the proper of licenses for each developer on your project.
See the Licensing topic for more information on licensing requirements.
Do Not Use Our Product Installers on End User Machines
You do NOT need to use our product installers to place our controls on end user machines, nor are you permitted to apply your license key on end user machines.
If you are getting license popups on end user machines, your licensing configuration is incorrect on your build machine. Read the Licensing topic to troubleshoot the issue. Once licensing is configured properly, you should only need to xcopy our product assemblies into the same folder as your application on end machines.
Do Not Install Our Controls to End User GAC (Global Assembly Cache)
We ask that you do not place our .NET Framework-based control assemblies in the GAC of end user machines. Our controls should only be in the GAC of developer machines, which is done by our product installer.