Closed PrisonerZERO closed 1 year ago
UPDATES: I can resolve the types by-hand in a separate unit test, so Lamar does seem to understand the classes exist...
var resolver = container.GetInstance<IAuditResolverOf<ContextType>>();
var helper = container.GetInstance<IWindowsIdentityHelper>();
So, it seems that the problem is Lamar doesn't recognize the registration of Generic<T>
as "Interface Properties".
Thanks for any help...
POST SCRIPT: The link to Generic Types on the Auto-Registration and Conventions page is 404
I have a (vanilla)
Generic Repository
class that also contains aGeneric Interface Property
.Each
Generic Repository
within theUnitOfWork
resolves...butLamar
seems to ignore theInterface Property
embedded within the repository class.All types are registered, so it "should" resolve within each one...but doesn't.
All types are registered, so it "should" resolve within each one...but doesn't.
Do I need to create some kind of builder?
NOTES:
IAuditResolverOf<>
into a "test class" & it didn't resolve there either?FOR EXAMPLE:
The following portion of my Unit Test fails...
THE CODE:
Some code excluded for brevity...
LAMAR CONFIGURATION REPORT:
Built by calling
WhatDoIHave()
. As you can see it understands whatIAuditResolverOf<>
maps to.