COM object?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   before considering an upgrade from a very old iSed version..
Is this now a managed code lib/assembly or is it still the old com class with all the registration issues of the old iSed Active X object?

If it has not changed, is there any plans for a managed assembly?

Thanks..

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ray Members Profile Find Members Posts Beginner Joined: 02 Jul 09 Status: Offline Points: 5	Post Options Post Reply Quote ray Report Post Thanks(0) Quote Reply Topic: COM object? Posted: 02 Jul 09 at 1:54AM
	before considering an upgrade from a very old iSed version.. Is this now a managed code lib/assembly or is it still the old com class with all the registration issues of the old iSed Active X object? If it has not changed, is there any plans for a managed assembly? Thanks..

Ingo Members Profile Find Members Posts Moderator Group Joined: 29 Oct 05 Status: Offline Points: 3529	Post Options Post Reply Quote Ingo Report Post Thanks(0) Quote Reply Posted: 02 Jul 09 at 6:20AM
	Hi Ray! It's still unmanaged code but it's possible to use QuickPDF (mainly the activex-version) in .NET-environments. Have a look here in the samples-section ... there is a C#-sample, too: http://www.quickpdf.org/forum/using-c-and-the-dll-edition-of-quick-pdf-library_topic1110.html Here are more samples with the normal dll and the activex-version for C#: http://www.quickpdflibrary.com/samples/index.php The QuickPDF-package offers a cs-file to create a mangaed code wrapper class around the activex-module. About future plans with real .NET-versions of the library perhaps one of the authors can tell something more if they look around here. If you have any suggestions for future plans you can post them here: http://www.quickpdflibrary.com/support/feature-request.php Cheers and welcome here, Ingo Edited by Ingo - 02 Jul 09 at 6:23AM

ray Members Profile Find Members Posts Beginner Joined: 02 Jul 09 Status: Offline Points: 5	Post Options Post Reply Quote ray Report Post Thanks(0) Quote Reply Posted: 02 Jul 09 at 9:09AM
	As above I currently have a licenced iSed version and know the very well the problems with com objects and dotnet.. Its a pain.. It appears from your response that there has been no change in this area.. If there is no change, then will stick with the existing iSed version.. Was hoping that it would get some "commercial" work done on it to make it more useable.. It does some things lot better/easier then itextsharp (free) but com objects and unmanged code is too much of a deployment pain.. If it was managed code then would use it exclusively, but otherwise a mix of itextsharp ( most) and a bit of iSed where absolutley needed.. But thanks for the response..

Rowan Members Profile Find Members Posts Moderator Group Joined: 10 Jan 09 Status: Offline Points: 398	Post Options Post Reply Quote Rowan Report Post Thanks(0) Quote Reply Posted: 02 Jul 09 at 9:40AM
	Hi Ray, Short answer: there isn't a .NET managed version of Quick PDF Library, but as Ingo mentioned (and you already know), the ActiveX and DLL editions of the library can still be used with the .NET framework. > As above I currently have a licenced iSed version and > know the very well the problems with com objects and > dotnet.. Its a pain.. It appears from your response > that there has been no change in this area.. What are the specific problems you're experiencing? A high number of Quick PDF Library use the ActiveX edition of the library with C# and VB.NET and this has not been a problem area. Have you been experiencing any specific problems or is it that you just want to keep it all managed code where possible? > If there is no change, then will stick with the > existing iSed version.. There's been lots of changes in the latest version -- too many to list here, but if you check out the updates page, you'll see a full list of new features and improvements for the last three updates. > Was hoping that it would get some "commercial" > work done on it to make it more useable.. It is having commercial work done on it -- what areas do you find unusable? If you're just in need of a managed version, then we won't be able to help you out in the short-term, but if you're having problems with bugs or really need certain features, get in touch and we'll try to help you. Cheers, - Rowan. ___________________________ Quick PDF Library Team http://www.quickpdflibrary.com/

ray Members Profile Find Members Posts Beginner Joined: 02 Jul 09 Status: Offline Points: 5	Post Options Post Reply Quote ray Report Post Thanks(0) Quote Reply Posted: 04 Jul 09 at 12:04AM
	"What are the specific problems you're experiencing? A high number of Quick PDF Library use the ActiveX edition of the library with C# and VB.NET and this has not been a problem area." The normal problems, associated with activex, hassle deployments, and poor threading (COM object are realy like cleint server).. ect etc.. This has nothing to do with the library just that this technology no longer is usable within dotnet deployments.. Now if a "High number of user use C# and VB)" then I would suggest that you need a managed library? "There's been lots of changes in the latest version -- too many to list here, but if you check out the updates page, you'll see a full list of new features and improvements for the last three updates." I did look, nothing we need, the old libray funtionality works fine, its the old implementation/deployement techology thats the issue. We have Zero unmanaged code libraries, and will not buy any new libraries which are not manged code.. Too much pain.. Suspect 100% of your dotnet users would agree.. No one is going to say I would prefer to use unmanged code vs manged code ... zero... "If you're just in need of a managed version, then we won't be able to help you out in the short-term," Thats fine.. just checking.. As mentioned iTextSharp works for 90% of the stuff the couple of times we need iSed ( mainly to mnaipulate metadata and combining of existing pdf documents, itext is realy page oriented and metadata support is too flaky) we can live with our old iSed library.. Thanks for the response..