Enterprise Library / Unity vNext
Greetings!
This is a public forum for you to suggest/vote on the ideas for future capabilities/updates to Enterprise Library and Unity.
Please note the list may not always represent the actual prioritized backlog of the development team.
3 results found
-
Same handlingInstanceID when an exception was already handled by the block
Exception Handling Application Block
It would be very useful if an exception that was already handled by the block uses the same handlingInstanceID generated the first time it was handled so you can associate all the exception chain as only one error.
If the exception was already handled the block uses the same handlingInstanceId generated before, if not then it generates a new one.
e.g. Supose that you show the handlingInstanceId to the user as a ticket number of the error. You want to track down what happen using that ticket number, but if your model handles the exceptions in…
9 votes -
Generic ITransientErrorDetectionStrategy
Hello,
ITransientErrorDetection.IsTransient accepts only an exception and it forces the code to throw exceptions even if not needed. I think it would help having an additional interface defined with a generic type, for examplepublic interface ITransientErrorDetection<T>
{
bool IsTransient(T error);
}This way it would still work with the current implementation of retry policy, but also allow cases when the error is not an exception but an error code or message. An example of usage would be with HttpClient which doesn't throw an exception when a return status code is an error
Thoughts?
Thanks,
Pedro4 votes -
Avoid needing to create a new ExceptionFormatter for a custom format.
Log exception using the log formatter of the logging category or define one inline.
3 votes
- Don't see your idea?