Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Please help me!!Please help me!!
Previous
 
Next
New Post
5/28/2008 11:46 PM
 

hello everyone..

i actually stil new with dotnetnuke and assigned by my bos to study about the credibility, relibility and sourceful..

so, i found that even i know about programming .NET a little bit mostly in vb.net, i would like to you all guys who is expert in this DNN to tell me is there any tutorial on how to look into the source code of DNN. I need to know because it's important if there any necessary additional module that i want to create alone and attach it with DNN.

thank you in advance..

 
New Post
5/29/2008 3:02 AM
 

Hi Farid,

I strongly suggest you not to start with digging into the DNN source. Devloping custom full featured modules just needs the main interfaces and types to be known, not the source code. DNN is built to be expandable through modules without modifications to the core. You can find many templates even for complete beginners here. Also, many books on Amazon are available.

Best regards,
Dario Rossa

 
New Post
5/29/2008 3:07 AM
 

I think you'll find the Source-version of Dotnetnuke very easy to work with in VS 2005 or 2008. 

I personally do a manual install of the source on my local IIS, dropping both the WebSite and Library folders into thier own subfolder, and pointing IIS to the "Website" folder.

Once the database is setup and the ininital installer runs, If I want to work with the full source...I just open the "DotNetNuke_VS2008.sln" file into VS 2008.
Most often I don't need to work with the full source when developing a module.  For this, I'll open VS 2005, and "Open Existing website".  Open "just" the DNN install, and then add my new module project to that.

This allows me to easily debug just my module-code when needed, and not have all the additional source assemblies loaded into my poor-ancient-computer at once.

And, as always, the links on this post are extremely helpful for module developers:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/74227/scope/posts/Default.aspx

 

 
New Post
5/29/2008 3:40 AM
 

Before you jump into trying to fathom the source code of what is a very complex portal framework.

I would first suggest you spend a good deal of time gettting to understand what DNN is capable of WITHOUT coding.

Once you understand how DNN works from an usability point of view - you will then come to understand that for many
situations there is often no need to resort to coding.

There is a huge wealth of prewritten modules available for DNN right now that meet the needs of many thousands of
users every day.

>>>>

Having said this - the next thing you need to come to terms with - is that you should always avoid touching
the source code of the framework itself - instead look to the existing methods of extending DNN in the form
of SKINS, SKIN OBJECTS, MODULES AND PROVIDERS - which all act a hooks into the framework without
actually altering the underlying code itself.

If after all this you still want to dig into the framework source code

 - install Visual Studio 2008 on your computer
 - download and install the SOURCE CODE version of the framework.
 - And open the 2008 solution thats in the root folder of the SOURCE CODE version using VISUAL STUDIO.

>>>>

From there get ready for a very long journey - this baby is big.

But first a comment.

The DNN source code is split into two parts - the LIBRARY and the WEBSITE.

The code in the LIBRARY folder is all compiled in advance into a set of .dll librarys that liv in the WEBSITE/bin directory.
These librarys make up much of the dnn framework and for the most part can be ignored unless you really want to
get into low level operations - or creation of providers etc

The WEBSITE contains all the files needed to make DNN run at RUNTIME - including a whole heap of compile on demand modules etc.

>>>

AS to how you go about getting started understanding how this all fits together - again - i would really suggest you get and understanding
of how to use DNN without code first.

And that means getting a running portal.

Once you have a running portal - you can then use VS2008 in debug mode to step thru the entire site line by line if that takes your fancy.

Westa

 

 

 

 
New Post
5/29/2008 4:31 AM
 

thank you for your reply..

actually, my job is studying DNN in part of its intergration. Because I currently have the intranet application such e-reporting using MS SQL Server 2005 Reporting Tools, application interface using ASP pages and users log-in their PC using Active Directory.

So, my point of suggestion is to integrate the log-in AD to the intranet application (just for internal user). For outside user (internet who can also log into some intranet application) they will use the specify given username and password.

This is because, I would like to apply Single Sign On (SSO), once you log-in the PC with your username and password, it will be go through the intranet application that applicable.

So, did you think it can be done? and please give some ideas..

thank you in advance..

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Please help me!!Please help me!!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out