Recommendations on the architecture of the plugin MVC3

I am trying to find more information on approaches to creating a plugin architecture.

I saw some good articles about MEF and MVC2, and Phil Haack mentioned some of the new extensibty interceptors available in MVC3 (http://haacked.com/archive/2010/05/16/three-hidden-extensibility-gems- in- Asp-net-4.aspx)

Has anyone seen good links to creating a plugin architecture for an MVC3 project?

I would rather use MVC3-specific technologies rather than just hack the MVC2 solution into an MVC2 environment.

Any ideas and suggestions would be greatly appreciated!

+3
source share
4 answers

, , MVC 1 2, "" 3?

10 , , :

http://stackoverflow.com/search?q= [asp.net-MVC] +

0

MVC 3 is the same basic architecture as MVC 2 and MVC 1. Each new version of MVC simply adds a few new features or slightly modifies the previous component.

If you find a solution for an earlier version of MVC, it is likely to work well, regardless of which version of the latest version will be at that moment, or with very minor changes.

0
source

Source: https://habr.com/ru/post/1786292/


All Articles