IronPdf Software Credits
Beyond our own C# development team, there are many to thank for the success of this .Net package.
Our first tribute is to Nuget.Org for providing a package manager for C# / .Net developers, which was sorely needed. We salute you. https://www.nuget.org/
We also wish to give great thanks to everyone involved in the .Net Core project. Crossing the platform barrier makes our lives as developers and sysadmins easier as we can finally code once and deploy anywhere. https://github.com/dotnet/core
Another warm hand to the Visual Studio IDE development team (possibly the best IDE ever created since Borland Delphi 7). https://www.visualstudio.com/ . We appreciate Microsoft's free community licenses which have made C# a new standard in academic software engineering, and the renewed support for Linux, BSD and MacOS shown with .Net core and Microsoft's continued support of Xamarin.
This software project is a cohesive solution to the functional issues users face when using PDF files in .Net.
To achieve the best end result at a reasonable cost to developers, our team ethically joins and makes use of community code projects wherever they give the best and most stable results. Each library is licensed fairly, as described in the linked project hubs below. Each and every community project is consistent with commercial use.
There is no need to install any additional software; everything you need to run this library is included in our download & nuget packages. All code is generally compiled into our software in such a way to avoid 'DLL Hell' and make installation easy for those teams who prefer not to use Nuget package manager.
Most often, we use community software projects 'as is'. Occasionally, we might find significant improvements to any of these community projects. We are glad to share our findings, specifically when those improvements may benefit other users.
Although it may have become commonplace for software publishers to overlook the use of liberally licensed source code in commercial software, we take the stance that transparency is the best policy: We have used the following software libraries in the development of this project, either as source, binary, proof of concept or inspiration.
References and Nuget Packages
- iTextSharp 4.1.6 LGPL/MPL
- iTextSharp Core 4.1.6 LGPL/MPL
Sometimes .Net is limited and can not yet achieve a certain task as well as C++. Hopefully this will resolve over the coming years with the huge growth of .Net Core. The software interacts with, and may deploy, the following community software libraries in binary format onto the end user machine, alongside their full license terms. There is nothing for you, the developer, to do here. We think it is correct for you to be fully informed that we use the following assemblies for .Net Interop.