@Alan,

If you re-read my answer I didn't say what you wanted to do was wrong.

You juxtaposed "I need this to do something for a client..." with "...where the code is that displays the modules on a page." I inferred, very possibly wrongly, that you wanted to use such code in a module. With the little information I have; I still think it sounds like a bad idea.

If I knew more about your use case I might change my opinion and think it a great idea. To find out more about your use case I asked why you wanted to do that.

In your reply you called me a "code nazi".

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

So, first things first:

Page rendering can generally be considered to begin in the Skin.cs code.  This code is responsible for rendering all the page elements.  The beginning of module processing begins in the ProcessModule method.  This will ultimately call down to the pane to begin rendering the module container which will then render the module.  The container will ultimately instantiate a ModuleHost, which instantiates a ModuleControlFactory which figures out what type of ModuleControl to instantiate (HTML5, Razor, MVC, WebForms).  Each layer in this chain is responsible for adding different parts of the chrome based on what mode the page is in, what permissions the user has etc.  Hopefully that should be enough to get you started.

As for the back and forth, we all need to remember that we need to remain civil. Using loaded terms like Nazi or Fascist creates an atmosphere which is not conducive to building community.  It is not always clear why someone is asking a question or why someone is answering the way they are.  We have all seen our share of mangled DNN implementations, so we shouldn't get upset if people are trying to help steer us away from going down that path.  

---

Joe Brinkman
DNN Corp.