Custom handling of unresolved types during LoadConfiguration()
I have large hierarchy of objects spread across several assemblies and deployment packages. I want to configure it once and reuse the same configuration file in several applications. I am looking for a way to instruct unity to ignore unresolved <register type=""> entry and continue registering other types.
For my case it would be sufficient just to ignore such types, but ideally this should be an event or callback delegate that would be called on each such event so that it could be handled appropriately.
12
votes
Aleksey Odintsov
shared this idea