StatusCodes class and HttpStatusCode enum

Question

Why there is System.Net.HttpStatusCode class and Microsoft.AspNetCore.Http.StatusCodes enum, when both of them seems to do the same?

Example:

public string Foo()
{
    int statusCode = StatusCodes.Status409Conflict
    // or
    int statusCode = (int)HttpStatusCode.Conflict

    return $"There is a {statusCode} here."
}

System.Net.HttpStatusCode probably works with the System.Net.Http system, where AspNetCore.Http.StatusCodes probably works with asp.net, a different framework. — SupaMaggie70 b, Jan 06 '23 at 16:14

Taqi ツ · Answer 1 · 2023-01-06T18:17:15.010

1

The HttpStatusCode Enum is are inside the system.Net namespace, which means you can use it anywhere, especially when you need to read information from an API.

StatusCodes Class are inside the Microsoft.AspNetCore.Http namespace

The next one is in use, the StatusCodes class gives you the codes as an int ,But in HttpStatusCode you have to cast them

Use them to position the code

edited Jan 06 '23 at 18:17

answered Jan 06 '23 at 16:34

Taqi ツ

61
7

Please format your answer better. Using backticks to encapsulate code and .Net keywords helps. – Tim Jarosz Jan 06 '23 at 17:53

Codingwiz · Accepted Answer · 2023-01-06T16:39:17.930

Cannot add this as a comment since I don't have the rep, but I use System.Net.HttpStatusCode in my Asp.Net Core 6 web app to check against a HttpResponse.StatusCode.

System.Net is present by default while Microsoft.AspNetCore.Http needs to be added as a dependency.

So use System.Net if you also have other services that depend on it (ex: IPEndPoint). No need to install a separate package.

You can find more info here

TLDR: This is all due to Asp.Net Core's messy ecosystem

StatusCodes class and HttpStatusCode enum

2 Answers2