by IDEAL Software Support » Wed May 20, 2015 7:13 pm
Please read about COM licensing in the help file titled "Programmer's Manual", chapter "Redistributing VPE" - to get a basic idea of how COM licensing works. If you instantiate a COM object by code - ie if it is not placed on a form - your programming tool should care for the licensing. If old ASP does not provide some guidance or helper API, you need to take yourself care of providing the runtime-license key. This has to do with the COM licensing procedure, it is not VPE specific. The interna is also described in the help file titled "Control Reference" for the use with MFC. See the chapter "MFC: Using the VPE ActiveX with the MFC without placing it in a Dialog Resource". Maybe ASP provides some equivalent helper API - we are not ASP experts.
Here is some explanation with a maybe better wording, regarding how COM licensing basically works:
The COM Licensing mechanism knows two different modes of operation:
- Design-Time
- Runtime
This works as follows:
As you enter your License Key in the VPE setup software in order to install the VPE SDK (Software Develeopment Kit) on your machine, the design-time license key of the VPE ActiveX is installed on the development machine. The design-time license key is for software development, i.e. it allows to insert the VPE Control on forms while developing applications. It also allows to run your application, of course.
When you place the VPE ActiveX at design time on a form in your application - i.e. when you are developing your application - the client (your programming tool) requests the RUNTIME-KEY from the ActiveX server (VPE) and stores it together with the form. The runtime-key is different from the design-time key, and it is generated by VPE on-the-fly.
If you later build your executable or deliverable application for shipment to your clients, the runtime key is automatically stored by your development tool within your application. This means the ActiveX can not be used on the target machine for software development purposes, it can only be used to let the VPE ActiveX run. When the ActiveX is invoked, your application will provide the runtime key behind the scenes to the ActiveX.
If you get the demo banner in VPE or any OLE License error codes regarding VPE when running your application, then something with the COM Licensing goes wrong. If you are not placing the ActiveX on a form, your tool must provide other ways to assist you in performing the licensing.
Note: regsvr32.exe has nothing to do with design-time or runtime license keys. It allows the ActiveX to register its GUID in the system.