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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedBest way to work with existing module source code?Best way to work with existing module source code?
Previous
 
Next
New Post
7/8/2010 3:23 PM
 
I just spent a couple hours with the Chris Hammond blog posts and setup my first real DNN 5.x dev machine.  Now I want to poke around in a modules source code just to see what's under the hood.   So what's the best scenario for working with a module like "Events" and it's source code, do I even need to install it first or can just open it as a new project?
 
New Post
7/8/2010 3:49 PM
 
I prefer using source version of the module (install same procedure as install version) and open solution in VS. if you configure output appropriately to /bin folder, you may see your changes directly after compile w/o need to install.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/8/2010 5:26 PM
 
Another tip is to put good comments around your changes. That way if a new version is released you can do a diff to see what changes you made and make sure they get moved over. Not commenting makes this a nightmare since you don't know if it was a change from the module team or from you.
 
New Post
7/8/2010 7:06 PM
 
Sebastian Leupold wrote:
I prefer using source version of the module (install same procedure as install version) and open solution in VS. if you configure output appropriately to /bin folder, you may see your changes directly after compile w/o need to install.

I think what Sebastian means there is that after you do a build (and point the DLL for the project you are building to build into the DNN/bin folder) you won't need to try to repackage and install the module.

He is correct about setting up the source versions of the module, install the SOURCE version, even over the INSTALL version if you already have that running, then open up the project.

No guarantees that the project will have the NANT scripts like my solution, but you can likely try to integrate those into other modules as well!


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
7/12/2010 5:28 AM
 
hi, i want to kno0w how to see and edit the source code of the website developed in dOTNETNUKE
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedBest way to work with existing module source code?Best way to work with existing module source code?


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