Maintenance and upgrades

If you purchase a license for a DlhSoft product version build (e.g. 3.1.9) of one of our component libraries (e.g. Gantt Chart Light Library), it will also:

• entitle you to obtain free resolutions for technical issues you discover and report to DlhSoft within the product during the guarantee period (see the product EULA); even after the guarantee period, DlhSoft will try to continue resolving such issues for free as the common interest is to obtain the best possible product;
• work without any upgrade payments for all components within the new builds of the same major and minor version (i.e. 3.1.10, 3.1.11, ...) released in the next year; you will just need to download the latest build from DlhSoft Web site and install the license file again to the new product build; you can get alerts when new builds are available by subscribing to the DlhSoft product news feed (e.g. the news feed for Gantt Chart Light Library);
• work without any upgrade payments for all previously existing components within all the new builds of the same major version and different minor version (i.e. 3.2.*, 3.3.*, ...) released in the next year; in other words, the license you have already purchased will continue to work if you use only components that previously existed in 3.1 builds; supplementary and optionally you can also get license renewals or full upgrades to new builds (3.2.*, 3.3.*, etc.) including the ability to use any new components included within such new minor version builds by paying a small percent of the standard price or a mathematically differential price between the previous license price (for 3.1.9 at the time of purchase) and the new license price (if it was increased; if the price didn't increase, the upgrade would be free or require a renewal instead, as DlhSoft decides based on specific factors);
• be able to upgrade to any new major version (i.e. 4.*, 5.*) if it targets the same platform (i.e. WPF in 3.5 SP1), or a new version of the same platform (i.e. WPF in .NET 4) by paying a mathematically differential price between the previous license price and the new license price (if it changed);
• may be able to upgrade (depending on platform compatibility and/or available upgrade paths decided by DlhSoft) to any new major version (i.e. 4.*, 5.*) if it targets a different platform or platform version (i.e. a new technology superior to .NET/WPF) by paying an appropriate upgrade price (decided by DlhSoft based on multiple factors that may be involved);
• may request and receive free updated source code archives from DlhSoft (if the source code archive was originally included as a supplemental benefit of the purchased license type) when new builds of the same major and minor version are released (i.e. 3.1.10, 3.1.11, ...) in the next year; when you need a more recent source code package or the minor or major version changed (i.e. 3.2.*, 3.3.*, ..., 4.*, 5.*, ...) and we may have added new components to the library and/or changed the platform version (i.e. the .NET Framework version), the source code renewals or upgrade wouldn't be free, and you will need to pay a small percent of the standard price, a mathematically differential price (if the platform didn't change), or an upgrade price to obtain the latest source code archive;
• note: upgrade prices may include a partial or full original renewal license price (according to the number of months that have passed since the original request, upon upgrading to a different license type or product edition).

The technical steps that you need to perform in order to use a new product build if you have purchased a license for a previous one are listed below:

1. You may need to purchase a new/renewal/upgrade license from DlhSoft for the new product build:
   • Required, if the new product build has a different major version number (e.g. 4.*) than the one you've purchased (e.g. 3.*) or if the new build has been released after more than one year since your original purchase;
   • Optional, if the new product build has the same major version number and a different minor version number (e.g. 3.2.*) than the one you've purchased (e.g. 3.1.*), provided that you intend to use only the same components which were already available in the originally licensed build, if the new build has been released after less than one year since your original purchase;
   • Not necessary/not available, if the new product build has the same major and minor version numbers (3.1.9) compared to the one you've purchased (e.g. 3.1.8), as you can use only the same components which were already available in the originally licensed build, if the new build has been released after less than one year since your original purchase;
2. Optionally, remove the previous build installation from your computer, searching and uninstalling it from the Programs screen of Control Panel;
3. Download and install the new build available on DlhSoft Web site;
4. Install your previous/upgraded/new XML license file obtained from DlhSoft to your computer using the License Manager tool from the new product build menu in Start Menu;
5. Apply the updated license to your Visual Studio application project (the executable target of your solution);
6. Ensure all DlhSoft library references from your Visual Studio solution (i.e. all Visual Studio projects) point to the new product build installation folder (by default the build number is included in the folder name).