Hello folks.  I've spent the last two days trying to find this answer on the web, and can't find it anywhere.  Specifically, I am trying to find out the code that instantiates a module on a page.  I assume it's called from an httpmodule, but I cannot find this anywhere.  Can someone familiar with the core point me in the right direction?

I need this to do something for a client, and I've been wondering for years, anyway, where the code is that displays the modules on a page. Thanks in advance for any help!

I've been doing web development for 20+ years and software development and architecture for over 30 years.  Have written Billboard top ten software, but thanks for your 'concern'.  I never in a million years thought I would receive a post like this, when asking a question about how stuff works.  I've been doing DNN development since 2003, and the final 'black hole' for me is understanding how DNN populates modules on a page.

Forgive me for wanting to learn something!  Shame on me...

I do appreciate your reply Joseph, but I've had to deal with code fascists for decades, and I've lost patience with people who, because they can't think of a good reason for something, immediately attack it as something 'wrong'.  I'm a big believer in positive energy, and responses like his don't add anything to a discussion, and most definitely not to the answer.

I used to participate in these forums a lot, when they were more active, but after being hired for way too many DNN projects *after* someone had already come in and completely screwed up the implementation by doing things like using DNN as a 'website', and not creating modules when adding new features, but just adding 'pages' to the websites.  It just became too energy draining to constantly have to fix bad implementations.  One was so bad I had to tell the client that it needed to be rewritten, and that is the *only* time in 30+ years I have ever made this recommendation.  So I swore off DNN development for five or so years and am just getting back into it now.

So I'm well familiar with how people can screw up a DNN implementation, and have seen it all, including not using moduleexceptions, hard-coding links instead of using the dnn tab functions, etc.  In fact, I believe that the fact that so many people went and built poorly implemented DNN projects for clients that I know for certain went over budget because they did not spend the time *up front* to understand how to do true module development, can't help but to have hurt the popularity of DNN in the marketplace.  So I can understand the motivation when people want to say something if the poster is not aware of DNN. But that still doesn't make it a good thing to do.  If you know the answer, say the answer, but then say, are you sure you want to do this?' Which is completely different from what was done... Hopefully we'll all learn from this and be better contributors.

But I would still, *never* make a post reply to someone and not offer the answer, but instead just say it's a bad idea.  I believe if you are going to add to a discussion, then you post. It's called constructive criticism, and having managed lots of programmers in my life, I know better than to say something critical, if it's not constructive.  It's just makes for a happier development environment and happy programmers are productive programmers. If you are going to say something that does *not* add to a discussion, then it's better left between you and your mirror...