I’m using PDF Kit 126.96.36.199. Whenever I use PdfFileSecurity.SetPrivilege on a PDF that has been created by PdfFileEditor.Concatenate, a NullReferenceException is internally thrown, caught, and ignored. This makes for a bad experience if you’re attached with a debugger and the debugger is set to break whenever an exception is thrown.
The issues you have found earlier (filed as 10117) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
I'm now using PDF Kit 188.8.131.52, but it does not fix this problem. If you update the Aspose.Pdf.Kit reference in the attached C# project to use version 184.108.40.206, it will still internally generate and ignore a NullReferenceException.
If you set the debugger to break whenever a CLR exception is thrown, you'll see it stop at the NullReferenceException. If you don't break when the exception is thrown, you'll see the following message in the debugger's Output window:
A first chance exception of type 'System.NullReferenceException' occurred in Aspose.Pdf.Kit.dll
Note: Aspose issue 10117 does fix the ArgumentOutOfRangeException issue I reported in another thread, but it doesn't fix the NullReferenceException issue reported in this thread.
This issue is logged as PDFKITNET-11235 in our issue tracking system. Our team will be looking into the matter and you’ll be updated via this forum as the issue is resolved.
We’re sorry for the inconvenience.