Specifically addressed in the PDC 2008 2nd Keynote by Scott Guthrie, MEF has a lot more to do with things like extending Visual Studio 2008 and other applications, without having to use all the COM and older technologies… A very good demonstration of extending the text edition in VS2008 was shown among other things. Start … Read more
any luck with that? I was reading this and think that’s what you’re looking for. I have exactly zero xp with MEF, but it looks promising. I hope I can scrape some hours of free time together at home to experiment with that. It would be ultra usefull to create some kind of modularized MVC … Read more
If you want to build an MVVM application (which you probably do for various advantages), then you want an MVVM framework. I would recommend Caliburn.Micro, as it is straightforward to implement following the examples on the Caliburn.Micro documentation page. It also has a very compelling convention over configuration mechanism, and uses an Actions system to … Read more
Just ran into this same problem. I finally found out that I catched different exceptions with the same name, like you did: catch (ReflectionTypeLoadException ex) { // … } catch (Exception ex) { // ex is not null! // … } Both are named ‘ex’. Changing one of both names solved this problem for me, … Read more
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