PDFlib 8 Windows COM/.NET Tutorial

Supply your license key at runtime using PDFlib’s set_parameter( ) function, supplying
license as first parameter, and the actual license key as second parameter (see also
Section 0, »Applying the PDFlib License Key«, page 9):
oPDF.set_parameter("license", "...your license key ...")
Error handling in COM. Error handling for the PDFlib COM component is done according
to COM conventions: when a PDFlib exception occurs, a COM exception is raised and
furnished with a clear-text description of the error. In addition the memory allocated by
the PDFlib object is released.
The COM exception can be caught and handled in the PDFlib client in whichever way
the client environment supports for handling COM errors. A more detailed discussion
of PDFlib’s exception mechanism can be found in Section 3.1.1, »Exception Handling«,
page 59.
Using PDFlib with Active Server Pages. When using external files (such as image files)
ASP’s MapPath facility must be used in order to map path names on the local disk to
paths which can be used within ASP scripts. Take a look at the ASP samples supplied
with PDFlib, and the ASP documentation if you are not familiar with MapPath. Don’t
use absolute path names in ASP scripts since these may not work without MapPath.
Note UNC path names don’t work in IIS.
The directory containing your ASP scripts must have execute permission, and also write
permission unless the in-core method for generating PDF is used (the supplied ASP
samples use in-core PDF generation).
You can improve the performance of COM objects such as PDFlib_com on Active Server
Pages by instantiating the object outside the actual script code on the ASP page, effectively
giving the object session scope instead of page scope. More specifically, instead
of using CreateObject (as shown in the example in the next section)