Autofac.Extras.Plugins
1.0.0
dotnet add package Autofac.Extras.Plugins --version 1.0.0
NuGet\Install-Package Autofac.Extras.Plugins -Version 1.0.0
<PackageReference Include="Autofac.Extras.Plugins" Version="1.0.0" />
paket add Autofac.Extras.Plugins --version 1.0.0
#r "nuget: Autofac.Extras.Plugins, 1.0.0"
// Install Autofac.Extras.Plugins as a Cake Addin #addin nuget:?package=Autofac.Extras.Plugins&version=1.0.0 // Install Autofac.Extras.Plugins as a Cake Tool #tool nuget:?package=Autofac.Extras.Plugins&version=1.0.0
Imagine you deploy an application with, say, a pipeline for transforming Maya binaries to some specific graphics-engine dependent format and another pipeline for transforming 3dsMax files to the same target format.
You have a whole lot of types which have to be differently implemented in both pipelines, even though they stick to the same contracts. And you are using Autofac. So you need a way to easily tell the container:
- this is a component to be used in the context of the Maya pipeline
- this is a component to be used in the context of the 3dsMax pipeline
- this component X should be used by all pipelines
- for the Maya pipeline, please override X with Y
If this scenario sounds familiar to you, this Autofac.Extra is for you.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net is compatible. |
-
.NETFramework 4.6
- Autofac (>= 4.2.1)
-
.NETStandard 1.1
- Autofac (>= 4.2.1)
- NETStandard.Library (>= 1.6.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.0 | 2,171 | 12/29/2016 |
Initial release.