Skip to content

Move ProblemDetails outside of Asp.Net Core #58551

Open

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When creating a C# client library for an API which uses ProblemDetails currently the best solution I can find is to include a FrameworkReference to Asp.NetCore in that client library.

Of course you can generate or hand write a ProblemDetails class for the client project but it gets tedious with inheritence for custom problem details.

Describe the solution you'd like

I would like ProblemDetails to be available outside of asp.net core. Maybe somewhere near HttpClient or somewhere in the BCL? Or a NuGet package (possibly not as I understand the asp.net project would not like to have NuGet dependencies)?

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    area-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templates

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions