AspNetCore.Docs
AspNetCore.Docs copied to clipboard
dotnet
Problem details /2
Public review of the doc build:
- download the HTML files
- unzip
- view HTML file in a browser.
- For links outside the doc, remove the
review.from URL. @sammychinedu2ky start at
Client error response
Public review of the doc build:
- download the HTML files
- unzip
- view HTML file in a browser.
- For links outside the doc, remove the
review.from URL. @sammychinedu2ky start atClient error response
Thanks @Rick-Anderson 😅, but I wasn't able to see how the problem was resolved since the controller writes the problem details to stream before the middleware handles it.
Since there is no way around it than changing the controller like this:
Should I leave the code in the issue as it is since you explained why in the post?
Should I leave the https://github.com/dotnet/AspNetCore.Docs.Samples/issues/60as it is since you explained why in the post?
No, do a PR and create a 3rd controller named Values3Controller. After explaining the problem we'll show the work around.
Should I leave the https://github.com/dotnet/AspNetCore.Docs.Samples/issues/60as it is since you explained why in the post?
No, do a PR and create a 3rd controller named
Values3Controller. After explaining the problem we'll show the work around.
I can only see one controller from my end or am I mistaken?
https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/fundamentals/middleware/problem-details-service/Controllers/ValuesController.cs#L39
2 controllers, one file. Put the 3rd controller in the same file.
https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/fundamentals/middleware/problem-details-service/Controllers/ValuesController.cs#L39
2 controllers, one file. Put the 3rd controller in the same file.
Ooh I need to pull, I don't have this locally 😅
Ooh I need to pull, I don't have this locally 😅
Never do a PR from your old branch.
Ooh I need to pull, I don't have this locally 😅
Never do a PR from your old branch.
Sure thanks
The sample app ~also~ contains the following database context class:
dead wood
The sample app ~also~ contains the following database context class:
dead wood
Does "dead wood" mean something special here? 😂
