Hi, we have been using Unity in the azure environment and have written our ObjectBuilder wrapper class to traverse the executing directory and find all dependencies in the assemblise it finds. It does this by inspecting the classes in each assembly for one
that implements IObjectBuilderInitialiser and invokes a Register(IObjectBuilder objectBuilder) method which registers all the dependencies in that assembly.
It works really well, in the azure environment as there is
no GAC (that we install in) and everything the application needs is in the same directory. However, now we come back to more conventional development we are again working with the GAC.
Our ObjectBuilder wrapper for Unity is now in the GAC, meaning that when it initialises - it will not find any of the applications assemblies and therefore not find any dependencies.
We've taken this approach as we were finding the .config unity section becoming unwieldy.
Anyway, is there an approach we can take with Unity in this respect that will allow the dependencies of an application to be discovered? Don't pay too much heed to our original approach at the top - we are open to all suggestions.