In an ASP.MVC app, how to define a View and bring it in from an assembly?

Question

I am writing an ASP.MVC application that behaves as a host of future plug-ins that are yet to be written. These plugins will be packaged as DLL in separate assemblies. One of the things that a plugin is responsible for is to provide its own View. Preferable that the main app will not have to be recompiled, each time a new plugin is written. What is the best way to have the main app looking for views that are in other assemblies?

UPDATE: My last resort is to to leverage the Post-Build events to copy View files to the View folder of the main app. But I am looking for a better way.

Cool question! Will you also support partial views?

anon
– anon

2011-02-02 01:44:17 +00:00
Commented Feb 2, 2011 at 1:44 — anon
– anon, Commented Feb 2, 2011 at 1:44

stoic · Accepted Answer · 2013-11-21 17:56:34Z

1

Have a look at the mvcms project which does exactly what you are trying to do.

edited Nov 21, 2013 at 17:56

answered Feb 2, 2011 at 9:40

stoic

4,83815 gold badges64 silver badges88 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

In an ASP.MVC app, how to define a View and bring it in from an assembly?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related