Ether.Outcomes 2.9.5

.NET Standard 1.3 .NET Framework 4.0
NuGet\Install-Package Ether.Outcomes -Version 2.9.5
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.
dotnet add package Ether.Outcomes --version 2.9.5
<PackageReference Include="Ether.Outcomes" Version="2.9.5" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Ether.Outcomes --version 2.9.5
#r "nuget: Ether.Outcomes, 2.9.5"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Ether.Outcomes as a Cake Addin
#addin nuget:?package=Ether.Outcomes&version=2.9.5

// Install Ether.Outcomes as a Cake Tool
#tool nuget:?package=Ether.Outcomes&version=2.9.5

Outcome.NET uses generics and a fluent interface to add metadata to your return value. It's a very expressive, clean  result wrapper.

Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows
.NET Core netcoreapp1.0 netcoreapp1.1 netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard1.3 netstandard1.4 netstandard1.5 netstandard1.6 netstandard2.0 netstandard2.1
.NET Framework net40 net403 net45 net451 net452 net46 net461 net462 net463 net47 net471 net472 net48
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen30 tizen40 tizen60
Universal Windows Platform uap uap10.0
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on Ether.Outcomes:

Package Downloads

Simple abstractions for *Command and *Query parts of CQRS pattern


Simple database-adapted abstractions for *Command and *Query parts of CQRS pattern


Outcome.NET uses generics and a fluent interface to add metadata to your return value. It's a very expressive, clean result wrapper. Outcome really shines when you're orchestrating complex logic, because the fluent interface makes it easy to roll up messages from multiple methods, and even from unusual sources like exceptions. The resulting code is very clean, and is great way to implement the Notification pattern.


Notif.Abstractions - notificaion abstractions for .NET Standard

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.9.5 61,207 10/9/2018
2.9.4-beta 834 3/1/2018
2.9.3-beta 599 3/1/2018
2.9.2-alpha 2,157 1/18/2018
2.9.1-alpha 623 11/6/2017
2.9.0-alpha 609 10/24/2017
2.8.2-alpha 679 3/28/2017
2.8.1-alpha 759 1/10/2017
2.8.0-alpha 709 1/10/2017
2.7.0-alpha 690 10/19/2016
2.6.0-alpha 748 8/18/2016
2.5.0-alpha 742 8/12/2016
2.4.0-alpha 710 7/19/2016
2.3.0-alpha 758 5/31/2016
2.2.0 10,362 11/25/2015
2.2.0-alpha 778 6/22/2015
2.1.1-alpha 767 6/17/2015
2.1.0-alpha 739 6/17/2015
2.0.2-alpha 741 5/7/2015
2.0.1-alpha 971 4/29/2015
2.0.0-alpha 777 3/30/2015
1.3.1 1,176 3/27/2015
1.3.1-alpha 798 3/26/2015
1.3.0-alpha 757 3/23/2015
1.2.0 1,189 2/11/2015
1.1.0 1,406 11/14/2014
1.0.5 1,191 10/30/2014
1.0.4 959 8/7/2014
1.0.3 949 6/21/2014
1.0.2 892 6/17/2014
1.0.1 889 6/17/2014
1.0.0 952 6/17/2014

Fixed an issue where StatusCode was not included in FromOutcome. Changed this so that StatusCode is now backed by the Keys dictionary. Since StatusCode is a property, it should still be serialized the same way, so this is not a breaking  change for the edge case where an Outcome is serialized to Json and StatusCode is expected.