Can a MEF application built on .NET 4 import types built against .NET 3.5? -


I am developing a host application using the Management Extensibility Framework and it Designed against the NET 4 and System.ComponentModel.Composition assembly is built in the framework I would like to support the ability to develop parts using .NET 3.5 and would like to export them declaratively.

Since the export features are in new.4 and thus can not be referred by the assembly of .NET 3.5, the best way to ensure the export of parts is not a new one. Is there an easy way to do this without applying a catalog of catalogs which uses some other mechanism to search for exports?

You can write a handler for which 3.5 version is requested, for IEF's NAT The 4th edition will come back. However, the handler that you write will be used only if the assembly can not be found using the basic binding argument, then you will need to ensure that 3.5 MEF DLL is not available, or possibly extension Relate the relational relations without referencing () to prevent that DLL from resolving.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -