We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Getting more useful report generation exception information

I'm busy evaluating aspose.words for .net (17.4.0). So far so good, however is there any way of getting more useful exception information?

When an exception occurs during the Report generation stage, there is very little information given back to help determine where the error is and how to resolve it.

A couple of examples to demonstrate:

Example 1. This expression in the template was used: <>
Problem: "Anny()" method does not exist.
Exception message: System.Collections.ListDictionaryInternal
Tag 'if' is not well-formed. A conditional expression should return a Boolean value.

From that it is very difficult to figure out that "Anny()" is actually the problem. Also impossible to tell where in the Template the invalid expression is.

Example 2. This expression in the template was used: <>
Problem: There is no closing bracket "]".
Exception Message: An error has been encountered at the end of expression 'customers.Name>>\r<<['. An expression is expected

Again, hard to tell that the expression is missing a bracket. Also impossible to tell where in the Template the error is.

Example 3. This expression in the template was used: <>
Problem: customers collection is empty.
Exception Message: The sequence is empty or does not contain a satisfactory element.

So from that it is impossible to tell what Expression caused that error. Additionally it is impossible to tell which Collection is in fact empty.

So, is there a way of getting more information about the error as demonstrated above?

If not, my feature request:

1. When there is a generation failure caused by one of the above, provide the full expression that caused the error (or contributed to the error).
2. The Page number in the Template of that Expression, possibly even where about on the Page the expression is
3. If needed, the Collection or Data element that was being referenced.

Much appreciated.
Hi there,

Thanks for your inquiry. We have logged this feature request as WORDSNET-15203 in our issue tracking system. Our product team will look into the possibility of implementation of this feature. Once we have any information about this feature, we will update you via this forum thread.

We apologize for your inconvenience.

The issues you have found earlier (filed as WORDSNET-16496) have been fixed in this update