

Hi,
usually RegAsm.exe “c:\Program Files\PDFCreator\PDFCreator.exe” /codebase should do the trick. There is another issue here: clsPDFCreator and clsPDFCreatorOptions no longer exist.
The COM interface was completely rewritten after version 1.7.3, all the detail can be found here:
http://docs.pdfforge.org/pdfcreator/2.2/en/pdfcreator/com-interface/
best regards,
Hi,

- check if a profile exists
- create a profile
- add a new pdf-printer, which is using that profile
Hi there,
Same issue here and cannot find RegAsm to execute…Am on Win10/VS 2013
Thanks to advise how to correctly register PDFCreator.
Cheers
Philippe
Hi there,
Same issue here and cannot find RegAsm to execute…Am on Win10/VS 2013
Thanks to advise how to correctly register PDFCreator.
Cheers
Philippe
Anyone?
Hi,
are you all running the current version 2.3.0?
For .NET projects you can reference the PDFCreator.exe.
Regasm is located in C:\Windows\Microsoft.NET\Framework\v4.0.30319\ on my machine, from the visual studio command line you should be able to call it without the path though.
Best regards,
Hi,
- check if a profile exists
- create a profile
- add a new pdf-printer, which is using that profile
Hi,
the printer handling is now all done in the printerhelper.exe, to add a new PDFCreator printer you can call printerhelper.exe /addprinter “printername”.It isn’t directly possible to tie a profile to a printer using com, but you can use SetProfileByGuid or SetProfileByName for each print job.
Please see http://docs.pdfforge.org/pdfcreator/2.2/en/pdfcreator/com-interface/user-manual/basics/workflow-comparsion-v1-7-v2/ for the reasons behind this and the general new workflow which is quite different but offers more flexibility.
best regards,
Thanks, I think I can work with that.