To further focus the development and maintenance of this proiect on the important features/topics we have to get rid of the Unity and CastleWindows support and NuGet packages of NitroNet.
We now longer have the capacity to maintain these packages and in some cases NitroNet is probably even used with other IoC frameworks.
So instead it's better if we deliver a table with all registrations (types, lifetime, etc...) which have to be done in the target IoC framework.
To further focus the development and maintenance of this proiect on the important features/topics we have to get rid of the Unity and CastleWindows support and NuGet packages of NitroNet.
We now longer have the capacity to maintain these packages and in some cases NitroNet is probably even used with other IoC frameworks.
So instead it's better if we deliver a table with all registrations (types, lifetime, etc...) which have to be done in the target IoC framework.