DryIoc vs Unity #3111
Unanswered
EuroEager2008
asked this question in
WPF
DryIoc vs Unity
#3111
Replies: 1 comment 3 replies
-
DryIoc does in fact support it, we just haven't had it configured by default. If this is something you need you can provide the rules like: var rules = DryIocContainerExtension.GetDefaultRules()
.With(Made.Of(FactoryMethod.ConstructorWithResolvableArgumentsIncludingNonPublic)) If I see some interest in having this be the default behavior it's something we can consider. In general though you are far better off with DryIoc. Unity is out of active development and there are a number of features it does not support. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This bug report: #3089
was immediately closed because I couldn't easily describe a repro (I thought I had to expose my clients assemblies to do that).
Just for the sake of order, I found out myself and perhaps other struggle (or perhaps it is so obvious to all other, but myself):
Unity accepts to resolve types with non-public constructors (at least internal is ok), however DryIoc throws a ContainerResolutionException if constructors are not public.
Beta Was this translation helpful? Give feedback.
All reactions