MichaelHoffmeisterFesto
commented
8 months ago Thank you for your comment, I understand your pain point.
During the time, I've had multiple occasions, where important exception details were "cut of" when passing exceptions. Therefore, I tend to add more details in these info strings than less. Passing exceptions is done by passing string. So, I am ending up in a situation, where tedious and error-prone string parsing and reformatting would be one valuable option. Right now, I don't think it pays of. The content of these strings comes from .NET, I do not format it by myself.
Another option would be to completely renovate the exception handling (including background tasks, passing exceptions, etc.) These are also very considerable efforts.
I just wanted to explain, first.
Best Michael
Is your feature request related to a problem? Please describe. I am dealing with many incorrect AASX files and I need to fix errors. The error messages of Package Explorer are very hard to read, especially because they repeat the same information over and over again.
Here's an example. The red redacted parts of the image are the original file name on my hard disk. The violet redacted parts are the buffered AASX file in the temp folder.
As you can see, the original name is repeated 8 times and the buffered file name is repeated 22 times.
This makes it so hard to find the actual error message.
Describe the solution you'd like I'd like to have a clear and concise error message with every relevant file name only mentioned once. In addition, the error message should be formatted or syntax highlighted in a way that one can distinguish between message and call stack.
Describe alternatives you've considered None.
Additional context None.