This first step is to download the iTextSharp DLL and load the assembly into PowerShell. System.Reflection.Assembly::LoadFrom('itextsharp.dll') iTextSharp can both read and write to PDFs. Reading Form Fields from a PDF. To read from a PDF, you simply open a the PDF Reader and read the each field you require. The package includes the assembly itself (winscpnet.dll) and a required dependency, WinSCP executable winscp.exe.The binaries interact with each other and must be kept in the same folder for the assembly to work.
PLEASE NOTE: iTextSharp is EOL, and has been replaced by iText 7. Only security fixes will be added
We HIGHLY recommend customers use iText 7 for new projects, and to consider moving existing projects from iTextSharp to iText 7 to benefit from the many improvements such as:
* HTML to PDF (PDF/UA) conversion
* PDF Redaction
* SVG support
* Better language support (Indic, Thai, Khmer, Arabic, Hebrew)
* PDF Debugging for your IDE
* Data Extraction
* Better continued support and bugfixes
* More modular, extensible handling of your document workflow
* Extra practical add-ons
* Encryption, hashing and digital signatures
iText is a PDF library that allows you to CREATE, ADAPT, INSPECT and MAINTAIN documents in the Portable Document Format (PDF), allowing you to add PDF functionality to your software projects with ease. We even have documentation to help you get coding.
iText 7 is available under AGPL and Commercial license. iText 7 community: itext7
iText 7 is a complete re-write of iText 5, allowing you to choose your adventure with add-ons, all based on a simple, modular code structure that is easy to use and well documented.
iText 7 includes pdfDebug, the first debugging tool that gives you a clear overview of your content streams and document structure as well as pdfCalligraph, allowing you to leverage advanced typography.
Several iText engineers are actively supporting the project on StackOverflow: http://stackoverflow.com/questions/tagged/itext
See the version list below for details.
Dependencies
This package has no dependencies.
Used By
NuGet packages (138)
Showing the top 5 NuGet packages that depend on iTextSharp:
| Package | Downloads |
|---|---|
| itextsharp.xmlworker PLEASE NOTE: iTextSharp is EOL, and has been replaced by iText 7. Only security fixes will be addedWe HIGHLY recommend customers use iText 7 for new projects, and to consider moving existing projects from iTextSharp to iText 7 to benefit from the many improvements such as:- HTML to PDF (PDF/A) conversion- PDF Redaction- SVG support- Better language support (Indic, Thai, Khmer, Arabic, Hebrew)- PDF Debugging for your IDE- Data Extraction- Better continued support and bugfixes- More modular, extensible handling of your document workflow- Extra practical add-ons- Encryption, hashing and digital signaturesThis DEPRECATED tool parses (X)HTML snippets and the associated CSS and converts them to PDF. It is replaced by iText7 pdfHTML addon https://www.nuget.org/packages/itext7.pdfhtml/ and iText 7 Community: https://www.nuget.org/packages/itext7/XMLWorker is an extra component for iTextSharp. The first XML to PDF implementation, is a new version of the old HTMLWorker that used to be shipped with iTextSharp. | |
| BaseLib | |
| itextsharp.pdfa PLEASE NOTE: iTextSharp is EOL, and has been replaced by iText 7. Only security fixes will be addedWe HIGHLY recommend customers use iText 7 for new projects, and to consider moving existing projects from iTextSharp to iText 7 to benefit from the many improvements such as:- HTML to PDF (PDF/A) conversion- PDF Redaction- SVG support- Better language support (Indic, Thai, Khmer, Arabic, Hebrew)- PDF Debugging for your IDE- Data Extraction- Better continued support and bugfixes- More modular, extensible handling of your document workflow- Extra practical add-ons- Encryption, hashing and digital signaturesThe iTextSharp.pdfa adds PDF/A-related functionality for iTextSharp. The same funcionality is present in pdfa module of iText 7 Community: https://www.nuget.org/packages/itext7/ | |
| itextsharp.xtra PLEASE NOTE: iTextSharp is EOL, and has been replaced by iText 7. Only security fixes will be addedWe HIGHLY recommend customers use iText 7 for new projects, and to consider moving existing projects from iTextSharp to iText 7 to benefit from the many improvements such as:- HTML to PDF (PDF/A) conversion- PDF Redaction- SVG support- Better language support (Indic, Thai, Khmer, Arabic, Hebrew)- PDF Debugging for your IDE- Data Extraction- Better continued support and bugfixes- More modular, extensible handling of your document workflow- Extra practical add-ons- Encryption, hashing and digital signaturesThis DEPRECATED library adds extra functionality for iTextSharp. Please use iText 7 instead. iText 7 Community: https://www.nuget.org/packages/itext7/ and iText 7 pdfSweep addon: https://www.nuget.org/packages/itext7.pdfsweep/ | |
| MvcRazorToPdf Create pdf documents within an asp .net mvc project by generating your views as normal but returning a PdfActionResult. This converts regular produced razor/html to pdf documents in the browser using the iTextXmlWorker. Please see the following URL for instructions and a demo link: https://github.com/andyhutch77/MvcRazorToPdf. This uses the newer version/licence of iText/iTextXmlWorker and can process the html that is produced from your views. |
Itextsharp.dll Download Free
GitHub repositories (14)
Showing the top 5 popular GitHub repositories that depend on iTextSharp:
| Repository | Stars |
|---|---|
| dotnet/docfx Tools for building and publishing API documentation for .NET projects | |
| aelassas/Wexflow An easy and fast way to build automation and workflows on Windows, Linux, macOS, and the cloud. | |
| open-rpa/openrpa | |
| tonyqus/toxy .net text extraction framework | |
| dreling8/Nop.Framework c# asp.net mvc base development framework from nopCommerce。 |
Version History
See Full List On Nuget.org
| Version | Downloads | Last updated |
|---|---|---|
| 5.5.13.2 | 210,390 | 9/14/2020 |
| 5.5.13.1 | 1,788,749 | 6/20/2019 |
| 5.5.13 | 3,492,637 | 1/31/2018 |
| 5.5.12 | 1,050,729 | 8/24/2017 |
| 5.5.11 | 1,175,217 | 3/20/2017 |
| 5.5.10 | 1,215,050 | 10/10/2016 |
| 5.5.9 | 904,581 | 3/17/2016 |
| 5.5.8 | 517,157 | 11/30/2015 |
| 5.5.7 | 296,617 | 9/17/2015 |
| 5.5.6 | 515,815 | 5/7/2015 |
| 5.5.5 | 247,775 | 2/16/2015 |
| 5.5.4 | 139,096 | 12/16/2014 |
| 5.5.3 | 217,540 | 9/25/2014 |
| 5.5.2 | 93,529 | 7/29/2014 |
| 5.5.1 | 115,184 | 5/20/2014 |
| 5.5.0 | 144,075 | 2/14/2014 |
| 5.4.5 | 127,662 | 12/6/2013 |
| 5.4.4 | 62,747 | 9/16/2013 |
| 5.4.3 | 26,158 | 8/1/2013 |
| 5.4.2 | 70,114 | 6/25/2013 |
| 5.3.3 | 109,589 | 10/8/2012 |
| 5.3.2 | 32,525 | 9/15/2012 |
| 5.2.0 | 48,512 | 3/8/2012 |
| 5.1.3 | 35,057 | 12/15/2011 |
| 5.1.1 | 60,275 | 7/27/2011 |
| 5.0.6 | 41,327 | 2/23/2011 |
| 5.0.5 | 134,158 | 1/12/2011 |
WinSCP .NET assembly exposes its full interface to COM. As a COM library, it needs to be registered before use. If you are going to use the COM interface, register the assembly using command below. You do not need to register the assembly, if you are going to use it directly as a .NET assembly, e.g. from C#, VB.NET or PowerShell.
Where the %WINDIR% is path to your Windows installation, what is typically C:Windows or C:WINNT. Note that you can keep %WINDIR% as this environment variable should be set on your system to point to the Windows folder. The Framework needs to be replaced by Framework64 to register the assembly for use from 64-bit applications.1 On 64-bit systems, you should generally register the assembly both for 32-bit (such as old versions of Microsoft Excel) and 64-bit applications. The <version> is version of .NET framework to register the assembly with. It is recommended to use the latest available, what currently is v4.0.30319. You may however use any framework version from 2.0 (v2.0.50727) up. Note that framework 3.0 and 3.5 do not ship with RegAsm.exe. For these versions use RegAsm.exe from 2.0.
Cached
Typical registration commands for .NET 4.0 on 64-bit system would be:
Itextsharp 5 Documentation
The above examples assume that WinSCPnet.dll is in current working directory. Otherwise you need to specify an absolute path to the .dll.