Registered: 1341521810 Posts: 5
Reply with quote #1
I have a number of PDF report pages written for iTextSharp V188.8.131.52 that I would like to use in ISD. The version of iTextSharp embedded in /application/bin/reports.dll looks like version 3.1.8 which does not support various features I use such as cell.MinimumHeight, and actually I am struggling to get any table to display.
I have tried to add the itextsharp.dll to the bin directory as in this post http://sjc.ironspeed.com/post?id=4856638 but i just get heaps of " ambiguous, imported from the namespaces or types 'iTextSharp.text" because I have references to two version of iTextSharp. Is there any way to force ISD to use the iTextSharp.ddl Thanks for any help.
Registered: 1163577447 Posts: 13
Reply with quote #2
This is an important question for me too. Anyone found a solution?
Registered: 1247170309 Posts: 223
Reply with quote #3
I don't use iTextSharp, but it occurs to me:
have you gone into Visual Studio, removed the existing reference to the iTextSharp.dll and then added it back in so that it points to the new dll ? That might clean up the ambiguities. __________________ Paul
Registered: 1409869367 Posts: 140
Reply with quote #4
Did anyone find a solution to this?
Registered: 1066224327 Posts: 1,656
Reply with quote #5
There are probably references to it in the baseclasses. I ran into this problem with MySQL a couple of years back. I ended up loading the BaseClasses project, changing the reference, and then recompiling the baseclasses.dll and copying that back into my application folder.
And that does work, but of course when you migrate to a newer version of Iron Speed, you will have to repeat the process again. HTH, __________________ Miles Gibson, MScIS Iron Speed MVP Senior Consultant, Principal Milestone Software Inc. http://www.ironspeedmvp.co m\localizer Email: firstname.lastname@example.org Milestone Localizer: Full Localization for your Iron Speed applications!