Greentube.Serialization.DependencyInjection 1.0.0-alpha2

This is a prerelease version of Greentube.Serialization.DependencyInjection.
dotnet add package Greentube.Serialization.DependencyInjection --version 1.0.0-alpha2
NuGet\Install-Package Greentube.Serialization.DependencyInjection -Version 1.0.0-alpha2
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="Greentube.Serialization.DependencyInjection" Version="1.0.0-alpha2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Greentube.Serialization.DependencyInjection --version 1.0.0-alpha2
#r "nuget: Greentube.Serialization.DependencyInjection, 1.0.0-alpha2"
#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 Greentube.Serialization.DependencyInjection as a Cake Addin
#addin nuget:?package=Greentube.Serialization.DependencyInjection&version=1.0.0-alpha2&prerelease

// Install Greentube.Serialization.DependencyInjection as a Cake Tool
#tool nuget:?package=Greentube.Serialization.DependencyInjection&version=1.0.0-alpha2&prerelease

Greentube.Serialization.DependencyInjection NuGet

By extending the Microsoft.Extensions.DependencyInjection it's possible to expose a simple fluent API to add a serializer to the container. With that, it's easy to consume ISerializer via dependency injection.

Two hooks are provided by this package. A SerializationBuilder and extensions on IServiceCollection directly.

Extensions to IServiceCollection

Consider you have an implementation of type NoOpSerializer.

class NoOpSerializer : ISerializer
    public byte[] Serialize<T>(T @object) => null;
    public object Deserialize(Type type, byte[] bytes) => null;

It could be registered like:

public void ConfigureServices(IServiceCollection services)

In case NoOpSerializer depends on some options:

class NoOpOptions { }

class NoOpSerializer : ISerializer
    private NoOpOptions _options;
    public NoOpSerializer(NoOpOptions options) => _options = options;

    public byte[] Serialize<T>(T @object) => null;
    public object Deserialize(Type type, byte[] bytes) => null;

Registration can be done as:

public void ConfigureServices(IServiceCollection services)
    services.AddSerializer<NoOpSerializer, NoOpOptions>(ServiceLifetime.Singleton);

The options type provided will use the framework Microsoft.Extensions.Options for configuration. That means that values provided to the options instance could be defined via configuration files in different formats and even environment variables. For more information on MEO, refer to Microsoft documentation.

Note that there's no dependency on IOptions<T> from NoOpSerializer's constructor. That allows decoupling between the assembly where NoOpSerializer was defined and Microsoft.Extensions.Options.


Besides adding the serializer directly to ServiceCollection, it's possible to use the builder. This allows other libraries to expose AddSerializer through their own builders and have a more fluent API when setting up libraries that require serialization.

public void ConfigureServices(IServiceCollection services)
    services.AddSerialization(builder =>

This assembly was created to allow implementations have their own extension methods like:

  • AddJson
  • AddProtoBuf
  • AddXml
  • AddMessagePack
  • etc

Which in turn simply call AddSerializer<T> with the desired lifetime while having their Options type also registered.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  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. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (6)

Showing the top 5 NuGet packages that depend on Greentube.Serialization.DependencyInjection:

Package Downloads

Extensions to configure Greentube.Messaging via Microsoft.Extensions.DependencyInjection.


Integration of Greentube.Serialization.Xml with Microsoft.DependencyInjection.


Integration of Greentube.Serialization.ProtoBuf with Microsoft.DependencyInjection.


Integration of Greentube.Serialization.Json with Microsoft.DependencyInjection.


Integration of Greentube.Serialization.MessagePack with Microsoft.DependencyInjection.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0-alpha2 2,052 11/26/2017
1.0.0-alpha 802 11/25/2017