build precompile after we add/change/remove modules or themes?

Topics: Customizing Orchard, Writing modules, Writing themes
Jun 25, 2014 at 2:17 AM
Edited Jun 25, 2014 at 2:52 AM
I am trying to understand when to run build precompiled. I think that, for best performance, we generally need to
  1. download the Orchard Source
  2. add/change/remove any modules or themes
  3. run build precompiled
  4. publish the result
  5. repeat steps 2 to 4 anytime we change a module/theme
  6. on a LIVE site, avoid installing modules/themes from the Gallery.
Here is my rationale. A fast site is one that has NO .csproj files, because best performance occurs when we don't do dynamic compilation. Modules from the Orchard Gallery come with a .csproj.

So, true or false? For best performance, avoid installing modules/themes from the Gallery on a LIVE site. Rather, install themes/modules locally, run build precompiled, and then publish the results.