CODEWITHSUNDEEP
asp.net-mvcarchitecturerazorvirtualpathprovider
Daniel Harvey
Daniel Harvey

Reputation: 379

Vertical asp.net MVC organization and VirtualPathProviders

I'm currently working on a relatively large MVC project I would like to organize vertically.

Why break convention? And, in more detail here

As far as implementation goes, the plan is a VirtualPathProvider. My question is, what would the best way be to give this VirtualPathProvider knowledge of the feature folder names?

e.g. ~/Features/{Feature}/View1.cshtml

Upvotes: 2

Views: 285

Answers (1)

Erik Funkenbusch
Erik Funkenbusch

Reputation: 93434

If you plan to do this, I would definately NOT use a VirtualPathProvider. The reason is that path searches are expensive. The more paths you have, the longer it takes to find them.

I would instead specify paths directly. You lose the convention aspect, but you gain performance.

Upvotes: 2

Related Questions