Blog

Reading Error Messages and Stack Traces: .NET Exceptions, Async Stacks and Angular NG Errors

A stack trace is read layer by layer, not top to bottom: the real cause usually sits in the inner exception starting with --->, and the root of 50 identical errors in a log is usually the first error in time order. With real output from .NET 10 we read InnerException chains, AggregateException, the stack lost to throw ex, ExceptionDispatchInfo, going from a ProblemDetails traceId to the log, source maps, and Angular 22's NG0100, NG0200 and NG0201 errors.