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.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 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
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    • 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 example

      public 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,
      Pedro

      4 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
      • 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
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
        • Don't see your idea?

        Enterprise Library / Unity vNext

        Feedback and Knowledge Base