Akka.DI.AutoFac 0.8.0

Akka.DI.AutoFac - BETA

AutoFac Dependency Injection (DI) support for Akka.NET

There is a newer version of this package available.
See the version list below for details.
Install-Package Akka.DI.AutoFac -Version 0.8.0
dotnet add package Akka.DI.AutoFac --version 0.8.0
<PackageReference Include="Akka.DI.AutoFac" Version="0.8.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Akka.DI.AutoFac --version 0.8.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Release Notes

__Dependency Injection support for Ninject, Castle Windsor, and AutoFac__. Thanks to some amazing effort from individual contributor (**[@jcwrequests](https://github.com/jcwrequests "@jcwrequests")**), Akka.NET now has direct dependency injection support for [Ninject](http://www.ninject.org/), [Castle Windsor](http://docs.castleproject.org/Default.aspx?Page=MainPage&NS=Windsor&AspxAutoDetectCookieSupport=1), and [AutoFac](https://github.com/autofac/Autofac).
Here's an example using Ninject, for instance:
// Create and build your container
var container = new Ninject.StandardKernel();
// Create the ActorSystem and Dependency Resolver
var system = ActorSystem.Create("MySystem");
var propsResolver = new NinjectDependencyResolver(container,system);
//Create some actors who need Ninject
var worker1 = system.ActorOf(propsResolver.Create<TypedWorker>(), "Worker1");
var worker2 = system.ActorOf(propsResolver.Create<TypedWorker>(), "Worker2");
//send them messages
You can install these DI plugins for Akka.NET via NuGet - here's how:
Ninject** - `install-package Akka.DI.Ninject`
Castle Windsor** - `install-package Akka.DI.CastleWindsor`
AutoFac** - `install-package Akka.DI.AutoFac`
Read the [full Dependency Injection with Akka.NET documentation](http://getakka.net/wiki/Dependency injection "Dependency Injection with Akka.NET") here.**
__Persistent Actors with Akka.Persistence (Alpha)__. Core contributor **[@Horusiath](https://github.com/Horusiath)** ported the majority of Akka's Akka.Persistence and Akka.Persistence.TestKit modules.
> Even in the core Akka project these modules are considered to be "experimental," but the goal is to provide actors with a way of automatically saving and recovering their internal state to a configurable durable store - such as a database or filesystem.
Akka.Persistence also introduces the notion of *reliable delivery* of messages, achieved through the `GuaranteedDeliveryActor`.
Akka.Persistence also ships with an FSharp API out of the box, so while this package is in beta you can start playing with it either F# or C# from day one.
If you want to play with Akka.Persistence, please install any one of the following packages:
Akka.Persistence** - `install-package Akka.Persistence -pre`
Akka.Persistence.FSharp** - `install-package Akka.Persistence.FSharp -pre`
Akka.Persistence.TestKit** - `install-package Akka.Persistence.TestKit -pre`
Read the [full Persistent Actors with Akka.NET documentation](http://getakka.net/wiki/Persistence "Persistent Actors with Akka.NET") here.**
__Remote Deployment of Routers and Routees__. You can now remotely deploy routers and routees via configuration, like so:
Deploying _routees_ remotely via `Config`**:
actor.deployment {
   /blub {
     router = round-robin-pool
     nr-of-instances = 2
     target.nodes = [""akka.tcp://${sysName}@localhost:${port}""]
var router = masterActorSystem.ActorOf(new RoundRobinPool(2).Props(Props.Create<Echo>()), "blub");
When deploying a router via configuration, just specify the `target.nodes` property with a list of `Address` instances for each node you want to deploy your routees.
> NOTE: Remote deployment of routees only works for `Pool` routers.
Deploying _routers_ remotely via `Config`**:
actor.deployment {
   /blub {
     router = round-robin-pool
     nr-of-instances = 2
     remote = ""akka.tcp://${sysName}@localhost:${port}""
var router = masterActorSystem.ActorOf(Props.Create<Echo>().WithRouter(FromConfig.Instance), "blub");
Works just like remote deployment of actors.
If you want to deploy a router remotely via explicit configuration, you can do it in code like this via the `RemoteScope` and `RemoteRouterConfig`:
Deploying _routees_ remotely via explicit configuration**:
var intendedRemoteAddress = Address.Parse("akka.tcp://${sysName}@localhost:${port}"
.Replace("${sysName}", sysName)
.Replace("${port}", port.ToString()));
var router = myActorSystem.ActorOf(new RoundRobinPool(2).Props(Props.Create<Echo>())
.WithDeploy(new Deploy(
new RemoteScope(intendedRemoteAddress.Copy()))), "myRemoteRouter");
Deploying _routers_ remotely via explicit configuration**:
var intendedRemoteAddress = Address.Parse("akka.tcp://${sysName}@localhost:${port}"
.Replace("${sysName}", sysName)
.Replace("${port}", port.ToString()));
var router = myActorSystem.ActorOf(
new RemoteRouterConfig(
new RoundRobinPool(2), new[] { new Address("akka.tcp", sysName, "localhost", port) })
.Props(Props.Create<Echo>()), "blub2");
Improved Serialization and Remote Deployment Support**. All internals related to serialization and remote deployment have undergone vast improvements in order to support the other work that went into this release.
Pluggable Actor Creation Pipeline**. We reworked the plumbing that's used to provide automatic `Stash` support and exposed it as a pluggable actor creation pipeline for local actors.
This release adds the `ActorProducerPipeline`, which is accessible from `ExtendedActorSystem` (to be able to configure by plugins) and allows you to inject custom hooks satisfying following interface:
interface IActorProducerPlugin {
   bool CanBeAppliedTo(ActorBase actor);
   void AfterActorCreated(ActorBase actor, IActorContext context);
   void BeforeActorTerminated(ActorBase actor, IActorContext context);
- **CanBeAppliedTo** determines if plugin can be applied to specific actor instance.
- **AfterActorCreated** is applied to actor after it has been instantiated by an `ActorCell` and before `InitializableActor.Init` method will (optionally) be invoked.
- **BeforeActorTerminated** is applied before actor terminates and before `IDisposable.Dispose` method will be invoked (for disposable actors) - **auto handling disposable actors is second feature of this commit**.
For common use it's better to create custom classes inheriting from `ActorProducerPluginBase` and `ActorProducerPluginBase<TActor>` classes.
Pipeline itself provides following interface:
class ActorProducerPipeline : IEnumerable<IActorProducerPlugin> {
   int Count { get; } // current plugins count - 1 by default (ActorStashPlugin)
   bool Register(IActorProducerPlugin plugin)
   bool Unregister(IActorProducerPlugin plugin)
   bool IsRegistered(IActorProducerPlugin plugin)
   bool Insert(int index, IActorProducerPlugin plugin)
- **Register** - registers a plugin if no other plugin of the same type has been registered already (plugins with generic types are counted separately). Returns true if plugin has been registered.
- **Insert** - same as register, but plugin will be placed in specific place inside the pipeline - useful if any plugins precedence is required.
- **Unregister** - unregisters specified plugin if it has been found. Returns true if plugin was found and unregistered.
- **IsRegistered** - checks if plugin has been already registered.
By default pipeline is filled with one already used plugin - `ActorStashPlugin`, which replaces stash initialization/unstashing mechanism used up to this moment.
MultiNodeTestRunner and Akka.Remote.TestKit**. The MultiNodeTestRunner and the Multi Node TestKit (Akka.Remote.TestKit) underwent some drastic changes in this update. They're still not quite ready for public use yet, but if you want to see what the experience is like you can [clone the Akka.NET Github repository](https://github.com/akkadotnet/akka.net) and run the following command:
C:\akkadotnet> .\build.cmd MultiNodeTests
This will automatically launch all `MultiNodeSpec` instances found inside `Akka.Cluster.Tests`. We'll need to make this more flexible to be able to run other assemblies that require multinode tests in the future.
These tests are not enabled by default in normal build runs, but they will at some point in the future.
Here's a sample of the output from the console, to give you a sense of what the reporting looks like:
The MultiNodeTestRunner uses XUnit internally and will dynamically deploy as many processes are needed to satisfy any individual test. Has been tested with up to 6 processes.

Version History

Version Downloads Last updated
1.3.9 22,500 11/1/2018
1.3.0 66,100 8/15/2017
1.0.8 27,752 5/2/2016
1.0.7 644 4/6/2016
1.0.6 2,158 1/18/2016
1.0.5 1,297 12/3/2015
1.0.4 1,934 8/7/2015
1.0.3 713 6/12/2015
1.0.2 505 6/3/2015
1.0.1 582 4/28/2015
1.0.0 460 4/9/2015
1.0.0-dev1504032244 381 4/3/2015
0.8.0 469 2/12/2015
Show less