I have developed my entire dot net nuke website online using various modules. The website is for a project and with the project i must submit all of the source code explaining which parts do what. How can i view the entire source code for each page or module so i can copy it into my report. Do I have to do this offline (eg. download the site to visual web developer), because i have done that but am, cannot seem to find any of the code for my site.
Any help would be so greatly appreciated, im nearing my deadline and really panicking!
Thanks
            Sam

Hi Sam,

Look under the "Downloads" icon at the top of the page.  If you download the source release of DotNetNuke, you'll find the source code for the framework components in the Library subdirectory.  The UI components are located in the Website directory; it's up to you to decide if the .aspx markup consititutes "code," or just to include the .vb files.

Links to core module source packages are also availabe on this page.  To save yourself a few clicks, make sure to click on the disk icon when downloading.  You'll be looking at all .vb files within the zip, and again it's up to your requirements whether to include the .ascx files.

Finally, you'll need to contact the developers of all third-party modules which you may have used.  Some will release their source for a fee, but you'll find that a hit-or-miss proposition. 

Hope this gets you started!

Brandon

Hey Sam,
I guess it would depend on what your actual assignment was as to whether using DNN was the correct choice.

DNN is a dynamic web portal framework, so there really isn't the usual page, page, page, method of putting together a web site. In actuality, there is only one "page" in a DNN site and that's default.aspx.  What happens is that at runtime, DNN figures out which virtual "page" the user wants to see then retrieves information from the SQL Server database to figure out which "modules" are on the page and where they are to be located on the page. Then DNN loads each module into the page and each module on that page is responsible for generating it's own output. The results is a combination of HTML and script that is sent down to the client's browser.  So, each module is responsible for "building" it's output from the database and DNN then merges the output from all the modules into a virtual page.

Realistically, you are using DNN as a "product" which allows you to combine modules to build a web site.  If you assignment was about programmatically building a web site, then it would probably be inappropriate to use DNN unless you develop your own module and then show the source code for your module and how it can be used within a DNN portal to display web content.