OK. Sorry. TL;DR is not really possible on this topic. You can however, jump to the final paragraphs for some (possibly) simpler (or required) alternatives to classic .NET licensing.
Once you purchase a development library license from DlhSoft, you will receive an XML file. You then install it for the software package (downloaded separately, e.g. previously, for trying out the components) and apply it to your development project.
The XML license file is all you need to make the trial nag screens go away. Because Microsoft licensing is complex, however, for the .NET Framework software you will need to follow a few steps to apply the license. These steps also depend on the way you have installed the software package in the first place (Setup, NuGet package, received it with cloning of a folder).
Assuming that you are using NuGet packages, that you are working on a Windows machine, and that you want to use DlhSoft License Manager – a tool that we provide to help you setup the license file with more ease, follow these steps:
- Using Windows Explorer, go to your solution folder, then to this subfolder: packages\DlhSoft.[product].[version]\lib\[target]. For example: [product] = GanttChartWebLibrary, [version] = 5.3.3, [target] = net45 (you will need to know what .NET version your project targets, and select the appropriate target subfolder within lib there);
- Extract LicenseManagement.zip file into a LicenseManagement subfolder: packages\DlhSoft.[product].[version]\lib\[target]\LicenseManagement;
- Run the License Manager tool by starting this executable file (signed by DLHSOFT SRL): packages\DlhSoft.[product].[version]\lib\[target]\LicenseManagement\LicenseManager.exe.
- In the License Manager tool, use Install link and select the XML file you have received. This will generate LIC files for individual components of the package in the same folder with the DLLs that Visual Studio will eventually use to license the components.
- But for Visual Studio to know which are the licensable components, a Licenses.licx file is also needed in your project. That is a simple text file, listing the .NET components with their assemblies. The License Manager tool can create/update the Licenses.licx file for you. Click Apply license link (after installation succeeded) and select the .csproj or .vbproj that you are working on (the executable one, if you have more project in a Visual Studio solution).
For .NET Framework licensing an (arguably) simpler alternative to all the steps above is to just call a SetLicense method for each component that you use, somewhere in your app’s initialization code, passing the entire XML as a string argument (ensuring you properly escape characters, if needed). You’ll find SetLicenses static method in a special namespace; the call will eventually be formed like this: DlhSoft.[Namespace].Licensing.[ComponentName].SetLicense(“…“).
Finally, for .NET Core and .NET 5 the SetLicense alternative is actually required (as the classic NET Framework licensing is not supported anymore.)
Let us know if you need more details or if yoy have any further questions about any of the steps by contacting DlhSoft Support.
Thank you for your interest!
You may read more technical details about Dlhsoft component licensing (and see a diagram guiding you through the process) here.