MaksIT.Results 2.1.0

dotnet add package MaksIT.Results --version 2.1.0
                    
NuGet\Install-Package MaksIT.Results -Version 2.1.0
                    
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="MaksIT.Results" Version="2.1.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="MaksIT.Results" Version="2.1.0" />
                    
Directory.Packages.props
<PackageReference Include="MaksIT.Results" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add MaksIT.Results --version 2.1.0
                    
#r "nuget: MaksIT.Results, 2.1.0"
                    
#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.
#:package MaksIT.Results@2.1.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=MaksIT.Results&version=2.1.0
                    
Install as a Cake Addin
#tool nuget:?package=MaksIT.Results&version=2.1.0
                    
Install as a Cake Tool

MaksIT.Results

NuGet License: MIT

Line Coverage Branch Coverage Method Coverage

HTTP-aware Result / Result<T> for .NET - model success and failure once, then map to ASP.NET Core IActionResult or parse the same wire shape from an HttpResponseMessage.

Target: .NET 10 (net10.0)

Why

Most Result libraries give you success/failure (and sometimes a typed error), then leave HTTP as a second mapping in the controller: domain NotFound → 404, Conflict → 409, and so on. That remapping is where APIs drift.

MaksIT.Results uses HTTP status codes as the outcome vocabulary. One type carries success/failure, messages, and a shared classification (NotFound, Conflict, TooManyRequests, ...). The service already decided the status; the controller calls ToActionResult().

That is not "leaking HTTP into the domain." Status codes are a mature taxonomy of outcomes that apply beyond the wire - including desktop, workers, and CLI:

Status idea Same idea outside the browser
404 entity / file / setting not found
409 concurrent edit / state conflict
401 / 403 not signed in / not allowed
422 validation failed
429 rate limit / throttle
503 dependency down / retry later
202 accepted, still processing

Compared to typical Result libs

Typical Result lib MaksIT.Results
Outcome model Success / Failure (+ custom errors) Success / Failure + HttpStatusCode
Controller mapping Invent codes, map again to HTTP Status already set; ToActionResult()
Failure body Often ad hoc RFC 7807 ProblemDetails
Client parse Rare / out of scope FromHttpResponseAsync / FromActionResult
Status factories Usually Ok / Fail (+ a few) Named 1xx-5xx factories

Bottom line: most Result packages stop at "return from a method." This one is a service ↔ API ↔ client result model - one contract from domain to wire and back.

Install

dotnet add package MaksIT.Results
Install-Package MaksIT.Results

Quick start

Create results

using MaksIT.Results;

Result ok = Result.Ok("Operation completed");
Result failed = Result.BadRequest("Validation failed");

Result<int> answer = Result<int>.Ok(42, "Answer generated");
Result<UserDto?> missing = Result<UserDto?>.NotFound(null, "Entity not found");

Map between result shapes

Result<int> source = Result<int>.Ok(42, "Value loaded");

Result<string?> asString = source.ToResultOfType(v => v?.ToString());
Result nonGeneric = source.ToResult();

Controllers

using MaksIT.Results;
using Microsoft.AspNetCore.Mvc;

[ApiController]
[Route("users")]
public sealed class UsersController : ControllerBase {
  [HttpGet("{id:guid}")]
  public IActionResult Get(Guid id) {
    Result<UserDto?> result = id == Guid.Empty
      ? Result<UserDto?>.BadRequest(null, "Invalid id")
      : Result<UserDto?>.Ok(new UserDto(id, "maks"), "User loaded");

    return result.ToActionResult();
  }
}

public sealed record UserDto(Guid Id, string Name);

HTTP clients

Parse responses produced in the same contract (JSON body, redirect Location, or problem+json):

using HttpResponseMessage response = await http.GetAsync(url);

Result bare = await Result.FromHttpResponseAsync(response);
Result<UserDto> typed = await Result<UserDto>.FromHttpResponseAsync(response);

Or reverse an IActionResult you already built:

IActionResult action = result.ToActionResult();

Result parsed = Result.FromActionResult(action);
Result<UserDto> typed = Result<UserDto>.FromActionResult(action);

ToActionResult() contract

Outcome Response
Result success Status code only
Result<T> success, non-null Value JSON body + status
Result<T> success, redirect status (300-303, 307-308) and non-empty string Value Redirect; status preserved on RedirectResult
Any failure ProblemDetails: status, title = "An error occurred", detail = joined Messages, content type application/problem+json

FromActionResult / FromHttpResponseAsync

Wire shape Result
Success, no body Success Result / empty Result<T>
Success JSON body Deserialized into Result<T>.Value
Redirect + Location Result<string> with that URL and redirect status
application/problem+json (or JSON with detail / title) Failure; messages from problem details

JSON options

ObjectResult uses the app's JsonSerializerOptions when configured via AddJsonOptions:

builder.Services.AddControllers()
  .AddJsonOptions(options => {
    options.JsonSerializerOptions.DefaultIgnoreCondition = JsonIgnoreCondition.WhenWritingNull;
  });

If none are registered, responses fall back to camel case.

Status code factories

Family Examples
Informational Continue, SwitchingProtocols, Processing, ...
Success Ok, Created, NoContent, ...
Redirection Found, MovedPermanently, PermanentRedirect, ...
Client error BadRequest, NotFound, Conflict, TooManyRequests, ...
Server error InternalServerError, ServiceUnavailable, ...

Use Result.* or Result<T>.* (e.g. Result<MyDto>.Ok(value, "message")).

Contributing

See CONTRIBUTING.md. Changelog: CHANGELOG.md.

License

MIT - Maksym Sadovnychyy (MAKS-IT)

Contact: maksym.sadovnychyy@gmail.com

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

NuGet packages (7)

Showing the top 5 NuGet packages that depend on MaksIT.Results:

Package Downloads
MaksIT.MongoDB.Linq

MaksIT.MongoDB.Linq is a .NET library designed to facilitate working with MongoDB using LINQ queries, providing a seamless and intuitive interface for developers to interact with MongoDB databases. The library abstracts common data access patterns, allowing for more efficient and readable code when performing CRUD operations, managing sessions, and handling transactions.

MaksIT.Dapr

MaksIT.Dapr Result facades for Dapr pub/sub, state, invocation, bindings, secrets, configuration, cryptography, sidecar, lock, actors, workflows, and HA work-lease helpers.

PodmanClient.DotNet

Podman API client for .NET — manage containers, images, exec sessions, and archives via the Podman REST API.

MaksIT.IdentityHub.Client

HTTP client for MaksIT Identity Hub API.

MaksIT.HAMode

Unified HA runtime coordination package for MaksIT services: abstractions and PostgreSQL, Redis, and etcd lease implementations.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.1.0 183 10/28/2026
2.0.6 292 10/27/2026
2.0.4 616 8/14/2026
2.0.3 511 6/28/2026
2.0.2 238 6/2/2026
2.0.1 168 3/8/2026
2.0.0 184 2/22/2026
1.1.1 259 11/3/2025
1.1.0 241 11/2/2025
1.0.9 187 10/31/2025
1.0.8 178 10/31/2025
1.0.7 249 10/29/2025
1.0.6 425 5/5/2025
1.0.5 352 9/28/2024
1.0.4 214 9/28/2024
1.0.3 215 9/28/2024
1.0.2 202 9/28/2024
1.0.1 216 9/28/2024
1.0.0 300 8/30/2024