Starting with PDFNet SDK 6.2.0-BETA for Windows Store apps, it is now possible to get more useful error messages when PDFNet throws exceptions.
Due to limitations of the COM API boundary, only System.Exception could be passed from the PDFNet SDK to the consuming code. This limited the errors to those that were already defined and prevented custom information to be attached.
To overcome this, PDFNet SDK for Windows Store apps has a new class; pdfnet.Common.Exception that can be created with an HResult from a System.Exception and will be able to display the information relevant to the error that caused the Exception.
The following code snippet shows an example in how to use the new PDFNetException class:
<br>string errText = "NONE";<br>try<br>{<br>pdftron.PDF.PDFDoc doc = new pdftron.PDF.PDFDoc("not_valid");<br>}<br>catch (Exception ex)<br>{<br>pdftron.Common.PDFNetException pdfNetEx = new pdftron.Common.PDFNetException(ex.HResult);<br>errText = string.Format("Exeption at line {0} in file {1}", pdfNetEx.LineNumber, pdfNetEx.FileName);<br>errText += Environment.NewLine;<br>errText += string.Format("Message: {0}", pdfNetEx.Message);<br>}<br>MessageDialog errorDialog = new MessageDialog(errText);<br>await errorDialog.ShowAsync();<br><br>
Will show the following error message:
This information will be very valuable to us if PDFNet throws an unexpected Exception. If you encounter an Exception while working with the PDFNet SDK for Windows Store apps, it is a good idea to include the full error from PDFNetException.ToSTring() with the description of the problem sent to our support team.