I just wasted 4 hours trying to get 1.7.1 to work using the COM interface on Windows 2008, it didn't work. I went back to 1.7.0 and it work. THIS PRODUCT IS A NIGHTMARE! I regret investing the time. I could have bought real software for the hours that I have put into this!
why not provide a fricken DLL instead of an exe for com users?
Nobody answers support questions and the search feature on this site is useless. Try searching for the word COM and you get 0 results?
Yes, I know it is freeware but for God's sake, either make a decent product or give it up.
Hi,
the search requires at least 4 chars, so if you had typed COM Interface you would have seen many results.
What benefits do you see in a dll?
Support questions are answered as soon as a solution is found.
We tested 1.7.1 before releasing it and there where no issues here, but without any info I can´t tell you what went wrong.
regards,
Robin
Thank you for your reply. I am no expert but it seems that most of the security issues are related to this running as an EXE. A dll that can integrate into a .NET application and not launching an application seems like a far better solution and hopefully would alleviate all of these security issues. I used other DLLs without any of these problems. For COM users we want the functionality without windows opening and we don't want alerts about new releases popping up etc. This defeats the whole purpose of trying to embed the COM into an Application!
Issues I have seen:
1) Was a nightmare to install on Windows Server 2007 SP2. I made so many system config changes from reading google that I am not even sure what worked and what didn't.
2) Was a nightmare to install on Windows Server 2008 SP2
3) Works great on Windows 7, the print quality is good but when you put it on a production server like Windows Server 2008 the print quality is far inferior to Windows 7, no answers why?
4) 1.7.1 COM did not work. The error message was that the class could not be found. In my DComConfig there was no longer an entry in PDFCreater as was in version 1.7. Yet the PDFcreator printer app worked fine.
4) Now I am suffering from an alert telling me a new release is available which is interfering with my web application.
I appreciate that this is freeware and i was excited about using an OpenSource solution but I am not happy that I probably have invested 20+ hours of development and troubleshooting and it appears this is not a reliable solution.
Hi,
you can disable the update notification in the PDFCreator options or the registry.
You can use the COM functionality without launching the .exe, but it is a remotely controlable window application by design.
Points 1-2 are a bit more complicated, as on our test machines install was very smooth without any problems, but then again it is impossible to test all possible system configurations.
Sometimes fixing issues for one enviroment brings up issues in the next and currently there is much focus on porting the PDFCreator to C#.
Why the print quality on the server is not the same as on the Win7 machine, is really strange. Did both run with default settings?
regards,
Robin
If it is the background color of the table, it is most likely a setting in the printing application.
(the result would be the same when printed to a physical printer)
What kind of file caused the error with COM?
I can gladly email you samples between Windows 7 and Windows Server 2007/2008 if you provide me a valid email address. The main difference is the background-color of the table cell object is not filling in.
Now suddenly I am getting an error when running from COM
"file is not valid for PDF conversion."
Yet when I print the same file manually thru the print Driver it prints file. THIS IS RIDICULOUS.