Prism - Bad idea to use it?

I am migrating from Windows Forms to WPF and trying to use Prism to satisfy the requirement that the application be plug-in oriented.

My problem is that there seems to be no support. I also heard that in some cases it is very leaky. I am developing an enterprise application, this is unacceptable.

If so, and it’s nice to start using Prism, are there any alternatives to building a composite application? The only thing I can think of is to use MEF.

+5
source share
1 answer

With Prism, you have the option of using Unity and / or MEF as an IoC / DI framework ... it is also quite extensible ... so you can connect various IoC containers if you want.

, WPF , . / ..

MEF, , , , Prism , . EventAggregator ..

, .

Microsoft, , System.AddIn/Managed Add-in Framework (MAF).... .

- , MEF :

/ , , SharpDevelop .

.... , , .

+5

All Articles