This project is read-only.

Best way to create various orchard sites using common functionalities

Topics: General
Aug 14, 2012 at 10:03 PM

I'm implementing some Orchard-based sites, so I will extend/override some of Orchard's functionalities, the extensions could be similar between them, so a common factor would be extracted, what's the best way to accomplish it, having the extensions on only one place (project/projects) and referencing them on each of the projects or having instead my extensions for each of the project (Note that this could be good for performance, but bad for updates), the contrary of the other approach...could I find a fair approach between performance and updates?

Aug 25, 2012 at 1:24 AM

What number of common modules are we talking about? I imagine if you would have one "common" module on which other modules are depending, I wouldn't worry much about decreased performance. That said, you should probably do some performance testing to be sure about any noticable decrease in performance.