I put in the request for VeryPDF, and have implemented it into our Webservice client. Things are working fine. There will still may be some tuning, but mostly it is working.
I use dynamic linking of the DLL (first time a PDF arrives for a client, which may be never). I then simply keep the DLL loaded. Also, I do not store the registration code in memory. I "build" it, then use it, and then make sure all memory buffers used temporarily are memset. There is no strings in my exe listing the reg code at all (or any part of it). I know that the usage like this was not specified in your "how to use", but this is something I do any time I have to deal with keys/reg codes, so that it is much more difficult for any end user to determine what the reg code is.
My question is on deployment. Exactly what needs to be deployed? Do I simply add the 3 dll files to the install script, and that is it? I notice an "encoding" directory with many Adobe postscript font files. The
>>My question is on deployment. Exactly what needs to be deployed? Do
>>I simply add the 3 dll’s to the install script, and that is it?
Yes, you are right.
>>I notice an "encoding" directory with many Adobe postscript font
>>files. The er seems to print just fine without them. Do
>>they have a purpose, or can they simply be left out of the installation data set?
If your PDF files are not contain CJK characters, you can ignore "encoding" folder, "encoding" folder is useful for CJK PDF files.