Julien R

FYI this pull requests 10 and 11 have been ported to the new PDFsharp 6 in https://github.com/empira/PDFsharp/pull/48 Also, we did a nuget package of PDFsharp 6 with additional features, including...

> > FYI this pull requests 10 and 11 have been ported to the new PDFsharp 6 in [empira/PDFsharp#48](https://github.com/empira/PDFsharp/pull/48) > > Also, we did a nuget package of PDFsharp 6...

> I tried your code snippet with the PNG file downloaded from this thread - and everything worked as expected. @ThomasHoevel With Core build? I hope also that github image...

Signature computation is working well, Signature seems to be correctly added to the Sig dictionary (hex string of signature decodes properly in https://lapo.it/asn1js/), BUT when opening the document in Adobe...

### Signature feature is now working > Signature computation is working well, Signature seems to be correctly added to the Sig dictionary (hex string of signature decodes properly in https://lapo.it/asn1js/),...

Last thing to handle now is the signature's appearance that seems to not be displayed properly.

> Hi, I tried with a trusted certificate but get the same error Does the certificate has a root certificate (+ intermediate certificate) + end user certificate? Is the root...

> Hi, I tried with a trusted certificate but get the same error Did you try in DEBUG or RELEASE build? I just pushed a fix for Release mode.

> Was using DEBUG, below is the adobe errors. Hi @ibrahimAliTecman, I fixed the issue on the byte range computation that was caused by extra spaces added in DEBUG mode...

I've just pushed [496c553](https://github.com/empira/PDFsharp/pull/48/commits/496c5535aacfa6ac9d8db1b4dd4953fe160083bb) that allows to define a custom appearance for the signature field. Since everything is working fine now, I'm setting the pr as ready for review. I...