Open
Conversation
# Conflicts: # itextsharp.nuspec # itextsharp.pdfa.nuspec # itextsharp.xmlworker.nuspec # itextsharp.xtra.nuspec # src/core/AssemblyInfo.cs # src/core/iTextSharp/text/pdf/PdfPublicKeySecurityHandler.cs # src/core/iTextSharp/text/pdf/crypto/AESCipher.cs # src/core/iTextSharp/text/pdf/crypto/AESCipherCBCnoPad.cs # src/core/iTextSharp/text/pdf/security/CertificateVerification.cs # src/core/iTextSharp/text/pdf/security/OcspClientBouncyCastle.cs # src/core/iTextSharp/text/pdf/security/OcspVerifier.cs # src/core/iTextSharp/text/pdf/security/PdfPKCS7.cs # src/core/iTextSharp/text/pdf/security/SignaturePolicyInfo.cs # src/core/iTextSharp/xmp/impl/XmpSerializerRdf.cs # src/core/itextsharp(VS2010).csproj # src/extras/iTextAsian/iTextAsian(VS2010).csproj # src/extras/iTextSharp.xtra/Properties/AssemblyInfo.cs # src/extras/iTextSharp.xtra/iTextSharp.xtra(VS2010).csproj # src/extras/itext-hyph-xml/itext-hyph-xml(VS2010).csproj # src/extras/itextsharp.pdfa.tests/Properties/AssemblyInfo.cs # src/extras/itextsharp.pdfa.tests/itextsharp.pdfa.tests(VS2010).csproj # src/extras/itextsharp.pdfa/Properties/AssemblyInfo.cs # src/extras/itextsharp.pdfa/itextsharp.pdfa(VS2010).csproj # src/extras/itextsharp.tests/Properties/AssemblyInfo.cs # src/extras/itextsharp.tests/itextsharp.tests(VS2010).csproj # src/extras/itextsharp.tests/packages.config # src/extras/itextsharp.xmlworker.tests/Properties/AssemblyInfo.cs # src/extras/itextsharp.xmlworker.tests/itextsharp.xmlworker.tests(VS2010).csproj # src/extras/itextsharp.xmlworker/Properties/AssemblyInfo.cs # src/extras/itextsharp.xmlworker/itextsharp.xmlworker(VS2010).csproj
danielgindi
force-pushed
the
portable
branch
from
935fba2 to
91a0578
Compare
danielgindi
force-pushed
the
portable
branch
from
0f599b1 to
a6b46fe
Compare
Contributor
🎉 Snyk checks have passed. No issues have been found so far. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I know that iText 5 is EOL, but for people who are trying to migrate to newer technologies, it becomes very complex do it all at once.
Allowing itextsharp to compile for .NET Standard removes this obstacle from the way.
This is a rebase of #39 on the latest.