Info
| Version: | 1.0.0 |
| Author(s): | Modern Ronins |
| Last Update: | Thursday, December 29, 2016 |
| .NET Fiddle: | Create the first Fiddle |
| Project Url: | https://github.com/ModernRonin/Autofac.Extras.Plugins |
| NuGet Url: | https://www.nuget.org/packages/Autofac.Extras.Plugins |
Install
Install-Package Autofac.Extras.Plugins
dotnet add package Autofac.Extras.Plugins
paket add Autofac.Extras.Plugins
Autofac.Extras.Plugins Download (Unzip the "nupkg" after downloading)
Dependencies
.NETStandard 1.1
- Autofac(>= 4.2.1)
- NETStandard.Library(>= 1.6.0)
- Autofac(>= 4.2.1)
Tags
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.