DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI 2024.0.12.12815

dotnet add package DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI --version 2024.0.12.12815
NuGet\Install-Package DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI -Version 2024.0.12.12815
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI" Version="2024.0.12.12815" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI --version 2024.0.12.12815
#r "nuget: DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI, 2024.0.12.12815"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI as a Cake Addin
#addin nuget:?package=DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI&version=2024.0.12.12815

// Install DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI as a Cake Tool
#tool nuget:?package=DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI&version=2024.0.12.12815

UI for ASP.NET Core Problem Result Extension

© 2024 DotNet Brightener

NuGet Version

Introduction

This is an extensions for ASP.Net Core applications that use the ProblemResult package. This package provides a UI for viewing information about a specific error / exception that can be thrown by the application.

Check out the ProblemResult package for more details on how to implement self-documented error objects.

Installation

You can install the package from NuGet:


dotnet add package DotNetBrightener.AspNet.Extensions.SelfDocumentedProblemResult.UI

Enable UI for viewing errors information

1. Enable generate XML documentation file in your projects / solutions.

Add the following code to the section <PropertyGroup> in your your .csproj file:

<GenerateDocumentationFile>true</GenerateDocumentationFile>

If you have multiple projects in your solution, you'll need to add the above code to all of the projects. Another way is to add that to the Directory.Build.props file in the root of your solution.

2. Configure the ASP.Net project to use the UI package.

Add the following code to your Startup.cs (if you use Startup.cs) or Program.cs (by default) file:


app.MapErrorDocsTrackerUI(options =>
{
    options.UiPath = "/errors-info-ui"; // this is where you can access the UI from your application
    options.ApplicationName = "Test Error"; // this is the name of your application
});

How this work?

When your application is configured to use UI package, the application will collect the error classes that are derived from IProblemResult. The error object when returned from the application, will now have type properties that leads to the information page of the error.

{
  "type": "https://localhost:7290/errors-info-ui#/WebAppCommonShared.Demo.Controllers.UserNotFoundError",
  "title": "User Not Found Error",
  "status": 404,
  "detail": "The error is thrown because the requested resource of type User could not be found",
  "instance": "/api/ExceptionTest/exception2/123",
  "data": {
    "userId": 123
  }
}

If developer / user opens the Url found in type property, they'll be able to see the information about the error. With the provided information, the developer can identify the issue and fix the issue easier. For the user, they can use this to seek support from developer.

Example

Given the error object defined as below:



/// <summary>
///     The error represents the requested object of type `User` could not be found
/// </summary>
/// <remarks>
///     The error is thrown because the requested resource of type `User` could not be found
/// </remarks>
public class UserNotFoundError : BaseProblemDetailsError
{
    public UserNotFoundError()
        : base(HttpStatusCode.NotFound)
    {

    }

    public UserNotFoundError(long userId)
        : this()
    {
        Data.Add("userId", userId);
    }
}

visiting the URL in type property will see an error page like following:

User Not Found Error

Description

The error represents the requested object of type User could not be found

Reason

The error is thrown because the requested resource of type User could not be found

Response HTTP Status Code

The request that encounters this error shall be responded with HTTP Status Code 404.

Additionally, refer to RFC 9110 Document Specification for Status Code 404.

Response Body

Below is the sample response body of the request that encounters this error. Depends on the error, there can be additional properties that help you identify the issue.

{
  "type": "https://localhost:7290/errors#WebAppCommonShared.Demo.Controllers.UserNotFoundError",
  "title": "User Not Found Error",
  "status": 404,
  "detail": "The error is thrown because the requested resource of type User could not be> >found",
  "instance": "{usually is URL of the request}"
}

The Description of the page is pulled from XML Document <summary> tag, and the Reason is pulled from <remarks> tag. The Response HTTP Status Code is the status code that the error object is associated with. The Response Body is the sample response body that the error object will be returned.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2024.0.12.12815 108 5/7/2024
2024.0.12.12814 85 5/7/2024
2024.0.12.12721 104 5/6/2024
2024.0.12.12702 91 5/5/2024
2024.0.12.12622 107 5/5/2024
2024.0.12.12514 80 5/4/2024
2024.0.12.12512 84 5/4/2024
2024.0.12.12510 81 5/4/2024
2024.0.12.12420 65 5/3/2024
2024.0.12.12319 44 5/2/2024
2024.0.12.12319-rc-2405021801 35 5/2/2024
2024.0.12.12318 36 5/2/2024
2024.0.12.12215 75 5/1/2024
2024.0.12.12011 74 4/29/2024
2024.0.12.11720 86 4/26/2024
2024.0.12.11719 78 4/26/2024
2024.0.12.11621 85 4/25/2024
2024.0.12.11523 79 4/24/2024
2024.0.12.11522 78 4/24/2024
2024.0.12.11417 94 4/23/2024
2024.0.12.11400 95 4/22/2024
2024.0.12.11316 89 4/22/2024
2024.0.11.10220 81 4/11/2024
2024.0.11.10120 72 4/10/2024
2024.0.11.10119 74 4/10/2024
2024.0.11.10115 75 4/10/2024
2024.0.11.9914 109 4/8/2024
2024.0.11.9901 83 4/7/2024
2024.0.11.9823 94 4/7/2024
2024.0.11.9401 90 4/2/2024
2024.0.11.9301 83 4/1/2024
2024.0.11.9206 90 3/31/2024
2024.0.11.9205 85 3/31/2024