Note: Adding the two godfathers of MEF/Autofac into the convo (they are microsofties so i'm sure they are busy ;) hehe)
Here's my 2c on that line of thinking. This link explains it better than I can: http://stackoverflow.com/questions/4701520/which-bootstraper-for-caliburn-micro "...MEF isn't a general purpose IoC container (unlike Unity, Autofac etc), and its focus is on the discoverability of types and their composition. It is suitable for composite applications where extensions can be discovered at runtime and integrated into the application's shell. Its strength is in the fact that supporting assemblies can be dropped into a specified folder and be picked up without any additional work. Unity etc are more general purpose and provide capabilities beyond MEF and in addition to object composition are also focused towards other dimensions of DI such as lifetime management and interception..." Personally I create my WPF creations with a focus of pluggable parts and re-use given I have both my themeing (Metro) down to a fine art in terms of how it plays a role in each WPF app I create along with various other common shared libaries etc that also get used in other WPF applications. Especially given I've created an Enterprise Service Bus (yet another one) for the mining industry where the UI layers is a constantly evolving moving target where as the server-side solutions typically are slow in growth... MEF seems to just play nice here.... but Autofac offers a bit more options to tinker around and get into loads more trouble with :) Irrespective of MEF/Autofac choice, CM still allows one and/or the other whilst also you can swap these out for Castle etc (ie other IoC) so i guess in the end we are all spoiled for choice? --- Regards, Scott Barnes http://www.riagenic.com On Wed, Nov 30, 2011 at 5:03 PM, Greg Keogh <[email protected]> wrote: > Caliburn Micro and autofac have been mentioned in this forum a few times > during the year with admiration. I’m now browsing the documentation on > Caliburn Micro to get the hang of what it claims to do, and so far it makes > sense and looks attractive. However, it might call itself “micro” but > there’s still a lot of stuff that will seem cryptic until I see clear > examples or can get into the head of the authors.**** > > ** ** > > CB documentation shows how it uses MEF. I was just wondering what the > relationship is between CB, MEF and autofac. Are there any dependencies > between them? Don’t MEF and autofac step on each other’s toes a bit? Some > clarification about this would be nice. I’ll keep reading in the meantime. > **** > > ** ** > > Cheers,**** > > Greg**** > > _______________________________________________ > ozwpf mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf > >
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
