Getting Started with Extending Visual Studio The Visual Studio SDK for 2010 The VS2010 beta forums Visual Studio 2010 New Features, Extensibility Points and Partner Opportunities Most of the information on add-ins is in the SDK.
When you use the ImportingConstructor attribute, the parameters to the constructor become imports. By default, what you are importing (the contract name) is based on the type of the parameter or property that your are importing into. So in this case the contract type for both your imports is string, and there’s no real difference … Read more
vs2013 -> tool -> option -> project & solution-> web project -> cancel use IIS Express 64 Hope this can help you!
Eventually what I have concluded about the MEF vs IoC container is as follows: MEF is preferred to be used when one has to deal with unknown types or a plugin based architecture. IoC containers are preferred to be used with known types. Moreover, MEF is an architectural solution for dependency injection Whereas, IoC containers … Read more
I’ll expand a bit on my comment, which reads: I’ve just started using Lazy, and find that it’s often indicative of bad design; or laziness on the part of the programmer. Also, one disadvantage is that you have to be more vigilant with scoped up variables, and create proper closures. For example, I’ve used Lazy<T> … Read more
The main difference is that with unity you will explicitly register each class you want to use in the composition: var container = new UnityContainer(); container.RegisterType<IFoo,Foo>(); container.RegisterType<IBar,Bar>(); … var program = container.Resolve<Program>(); program.Run(); In MEF on the other hand, you mark classes with attributes instead of registering them somewhere else: [Export(typeof(IFoo))] public Foo { … … Read more
The principle purpose of MEF is extensibility; to serve as a ‘plug-in’ framework for when the author of the application and the author of the plug-in (extension) are different and have no particular knowledge of each other beyond a published interface (contract) library. Another problem space MEF addresses that’s different from the usual IoC suspects, … Read more
I have accepted Alastair Maw’s answer, as it was his suggestion and links that led me to a workable solution, but I am posting here some details of exactly what I did, for anyone else who may be trying to achieve something similar. As a reminder, in its simplest form my application comprises three assemblies: … Read more
I haven’t found a really comprehensive page, but there are a few: Microsoft Docs Simple Example from a msdn blog Code Project’s Introduction to MEF (part 1) MEF 101 part A from Geek with Blogs MEF 101 part B Another MSDN blog, a little more history than tutorial
When boiled down, the main difference is that IoC containers are generally most useful with static dependencies (known at compile-time), and MEF is generally most useful with dynamic dependencies (known only at run-time). As such, they are both composition engines, but the emphasis is very different for each pattern. Design decisions thus vary wildly, as … Read more