For the record: I am an employee of iText Software.
Currently, .NET Core
and its associated UWP
standard are not supported by any iText projects. We conducted research on both of these new technologies and found that there were significant problems with their support due to drastic changes in some components of the .NET Core
software stack. You can read fooobar.com/questions/1011683 / ... for more details about my initial investigation at UWP
; The problems with .NET Core
very similar.
If and when .NET Core
is supported, it will probably only be in our new iText 7 project, which will not be backward compatible with iText 5 (also known as iTextSharp). The reason for this is that iText 5 is now only for maintenance, that is, fix releases, since it is being superseded by iText 7 in the user community.
iText 7 for .NET (meaning the .NET Framework
only) is actually the automatic iText 7 port for Java using the Sharpen
tool. This will remove the possibility of many unpleasant lingering errors that were used to pop up in iTextSharp 5 due to porting of gaps or errors. We are currently looking to see if there is a way to duplicate this workflow for .NET Core
so that we can support this without the need for manual porting and manual maintenance. I regret to inform you that we have not yet found such a tool, so we may have to investigate the creation of the Sharpen
tool. Currently, this is perhaps not surprising, not our highest priority as a company.
source share