We have build an application, that build PDF Documents. With 4.6 all works fine, but when we change to 4.7 we get the folowing Exeption on the Save Method.
System.NullReferenceException: Object reference not set to an instance of an object. at x3f91538e8c0de749.x2288a8cd3edf6dd5.xbc44195a646b6045(xb912e9429339cb81 x80010f902a1f736e, GraphInfo x736b266a990e018d, Single x0ec16e7032a0d6ea, Single xc1dc1ba06d52a7f0, Single x212c37708191618a, Single x4480de48a17d0d57) at x3f91538e8c0de749.x2288a8cd3edf6dd5.x69f91951eb100ba5(xb912e9429339cb81 x80010f902a1f736e, Pdf x6beba47238e0ade6, Table x1ec770899c98a268, xa65184d44a47025b xbbe2f7d7c86e0379) at x3f91538e8c0de749.x276fb33596224483.x7c61808921e5b719(xb912e9429339cb81 x80010f902a1f736e, Pdf x6beba47238e0ade6, xa65184d44a47025b xbbe2f7d7c86e0379, Boolean xf99b21d4fbe51f2d) at x3f91538e8c0de749.x4c849e0e778e539e.xe3d2f5ee6867cec8(xb912e9429339cb81 x80010f902a1f736e, Pdf x6beba47238e0ade6) at x3f91538e8c0de749.xaa36f84dba9d652f.x5ec1518f85fc1bbf(xb912e9429339cb81 x80010f902a1f736e, Pdf x6beba47238e0ade6) at Aspose.Pdf.Pdf.Save(String pdfFile)
How can i finde out in witch thema in my code the problem can be?
I thing we did not set a new Proerty corectly or something is in the wrong order. but with this kind of exception i have a big problem to find out whats wrong.
I am afraid it's pretty difficult to figure out the actual cause of this problem until or unless we are able reproduce it at our end. From StackTrace I think the issue might be occurring when you are trying to use GraphInfo object while setting border information for the table but I am not entirely certain about this reason. However, it is even complicated to figure out the issue when the code used to work with Aspose.Pdf for .NET 4.6.0 and is crashing with Aspose.Pdf for .NET 4.7.0.
Can you please try generating a sample application that can help us in rectifying this problem. We are really sorry for your inconvenience.
I have tested the scenario and I am able to reproduce the same problem. For the sake of correction, I have logged it in our issue tracking system as PDFNET-21004. We will investigate this issue in details and will keep you updated on the status of a correction. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />