Open kelltrick opened 2 years ago
I think exposing the command HRESULT on ServerErrorException
(https://github.com/dotnet/diagnostics/blob/main/src/Microsoft.Diagnostics.NETCore.Client/DiagnosticsClient/DiagnosticsClientExceptions.cs#L27) by either setting Exception.HResult
or adding a new property would be a great start such that the caller could make some informed decision on what to do next instead of just giving up. This would also allow the caller to provide custom messaging for specific problems and possible resolutions.
We should translate the HRESULT exception codes we receive from
DiagnosticClient
into meaningful human-readable descriptions of the codes.Background and Motivation
When we get an error from the
DiagnosticClient
it will look something like this:Proposed Feature
We should translate the code 0x8013135B into it's description "Not Yet Available". Full list of codes here: dotnet/runtime:/src/native/eventpipe/ds-types.h: line 127
The example above would look something like this: