See the Generating Serial Numbers in Code sample
Yes! Most installers support calling an external DLL or EXE during the installation. You can have the installer call your application during install with a special command line to indicate it is being installed and perform only the license validation.
However, in most cases there is no reason to integrate DeployLX Licensing with an installer. DeployLX handles license validation when the software is used on the machine. The installer should handle only copying the files to the machine. Then when the software is run for the first time DeployLX will prompt for a serial number.
The user can change the Time Zone of the machine without causing trouble to the license file. If they change the clock is rolled back, then DeployLX Licensing may detect this alteration and invalidate the license. All dates and times are normalized to UTC, which is why the time zone change does not affect the license. Changing the actual clock backwards will cause a problem. If your users change the clock back one hour, the license will fail. Restoring the time will result in a valid clock again. The user can wait until the real time matches what they had rolled the clock forward to, or the publisher (you) can issue a new serial number with a new expiration date. If the user is only dealing with time zone changes, the license will automatically be re-enabled after a one day (24 hour) period.
DeployLX Licensing can work with COM applications through COM Interop. You create a .NET assembly that would manage the communication between the COM app and DeployLX. The .NET assembly would then be protected by DeployLX Licensing.
The .NET framework must be present on the end user’s machine.
Yes, DeployLX will work on VMs as long as they remain as stable as a regular machine. If the VM creates a random MAC address for their NIC, it may appear as new each time it is restarted and creates problems. It is advisable that the VM at least uses a static MAC address. This holds true for not only your installation of DeployLX Licensing, but your customers as well.
DeployLX Licensing will work on Citrix without problem, but there is no special handling. Terminals are not tracked in any special manner. You can use the Application limit to control how many copies of the application can be running at a time on the host machine.
Yes, SharePoint is another ASP.NET technology and does not require any special handling. Working with SharePoint is like working with any other ASP.NET assembly.
It is unknown at this point, as SilverLight is untested with DeployLX Licensing. You may test it with our free trial. Any feedback is greatly appreciated.
There is no planned support for the Compact Framework.
ClickOnce is not meant as a distribution service for commercial products, rather it's primary intent is for enterprise distribution within an organization to distribute internal software to their employees without running installs on each machine. For this reason the security restrictions placed on ClickOnce applications is extremely limited and will severely limit the ability of the running software to interact with the host machine. A secure license system needs to be able to control certain aspects of the host system to maintain it's integrity. This security restriction makes it difficult to distribute licensed applications over ClickOnce but it can be done.
The following articles may prove helpful in deploying a trusted ClickOnce application