(Disclosure: I used to be on team that wrote MEF, and my current team (C#) use
it extensively throughout Visual Studio and our components)
As Scott mentioned, MEF is effectively an Dependency Injection/IoC container.
Do a quick read up on the benefits/downfalls of DI, and the same things apply
I once used both autofac and MEF together in a wpf project .. To this day
food doesn't taste the same anymore ;)
I personally have no issue with MEF it's really as I stated Pepsi vs Coke
argument there's not exactly a win/loss case here other than choose one
because you see a specific gain vs
MEF was built to put the PRISM genie back in its bottle. MEF is also the
in-house approach to the stuff Autofac and other IOC stuff do for you these
days as well. If you like to sprinkle [Import] [Export] throughout the code
base and are happy with its existence than it's really down to Pepsi vs
Scott,
I couldn't agree with you more. MEF feels one of those Patterns
Practices thing that gets pushed onto us by MS at times but everyone hates
and it's f* impractical in any real life scenario.
On Wed, Jun 3, 2015 at 4:09 PM, Scott Barnes scott.bar...@gmail.com wrote:
MEF was built to put
