In the documentation for PDF Converter for redistributing the runtime controls on client computers it states that the developer license key should be kept private. We use a revisioning software that has a maximum command line length of 256 characters. Guess what? That incredibly long license code that needs be passed to install.exe cannot fit in that space, along with the other switches. The only option I have is to use a batch file and attempt to execute it, however, I cannot guarantee that the batch file will remain hidden, or get erased. This prevents us from effectively "hiding" the license code.
Is there any plan in the near future to make the license code a bit more manageable?
Any suggestions on how I can get around this problem?
Command line length exceeded due to license code
Hello,
There are many ways to implement the license code.
You didn't specify which version of the PDF Converter you are using (Developer or End User), but as you mentioned 'redistribution' than I assume you are using the Developer version.
You can install the Developer version using Install.exe (without activating it) and then you will add the activation code to your application by calling EnablePrinter() right before your call to DriverInit and right before your printout command.
This is how activation of the Developer version is done: from inside your application.
Hope this helps
There are many ways to implement the license code.
You didn't specify which version of the PDF Converter you are using (Developer or End User), but as you mentioned 'redistribution' than I assume you are using the Developer version.
You can install the Developer version using Install.exe (without activating it) and then you will add the activation code to your application by calling EnablePrinter() right before your call to DriverInit and right before your printout command.
This is how activation of the Developer version is done: from inside your application.
Hope this helps