Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...Move a module from "Install" mode to "Source" to be able to modify.Move a module from "Install" mode to "Source" to be able to modify.
Previous
 
Next
New Post
1/23/2010 11:35 AM
 
Kevin Kiejko


Joined: 11/2/2008
Posts: 78

Hello,

I wanted to make a slight modification to one of the modules that comes with DNN just to serve a custom purpose on my website.  I coudn't find the code to make the modification, and a friend of mine told me it was because I used the "Install" version of DNN, and not the "Source".  But I just want to change one module, not the entire site.  Is there some way I can swap the install files for that module with the source?  What changes would be required?  I really don't want to have to rebuild the entire website just for one module.

Thanks,

Kevin
 
New Post
1/23/2010 1:32 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

Firstly, the source package of the DotNetNuke framework does NOT include the source packages of the "core" modules. Secondly, you do not need the source package of the DotNetNuke framework for module development, although I do like to keep a source installation of the current version available for examination of core API method calls, properties, etc.

Module sources are available on each module's download page at CodePlex. Most but not all of the "core" modules either have or are in the process of moving their source control from our previous internal source control repository to that provided for each extension project on CodePlex. So, you can either obtain source code from the extension's source package or by downloading the most recent change set (which is often a later version of code still in development)  from the project's Source tab.

Most module source packages can be installed in the same manner as the install package. Most often a package's source files are contained in a nested zip archive named resources.zip which will be automatically extracted during the install. Most module sources are developed as Website Application Projects (WAP) and include a solution/project file for Visual Studio. You will need to edit these (outside of VS) before opening to adjust the IIS website URL, etc. to match that of your development installation.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/26/2010 1:15 PM
 
Kevin Kiejko


Joined: 11/2/2008
Posts: 78

Bill,

You'll have to forgive my ignorance, but I'm kind of new at DNN (and .NET development really).  You say that "you do not need the source package of the DotNetNuke framework for module development", but how is that when I want to modify an existing module directly?

I did check out Codeplex and unfortunetly, the module I was looking to modify isn't listed.  I am running DNN version 04.09.00 and the module is the Vendor module (banners).  Do you know of some way to recover an old module for an older version of DNN?

So if I do eventually find the source for the module I'm looking for and I install it like any other DNN module, will it automatically replace the existing module?  I'm asking because I am currently using that module and have data in it's tables.

Thanks for the help.

Kevin
 
New Post
1/26/2010 7:59 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

Unfortunately, I will have to stand corrected as the Vendor/Banner functionality of DotNetNuke while appearing to be a module is actually part of the core framework and not a separate module project.

The usercontrols and their corresponding .ascx.vb code files are located in the Admin/Vendors folder of the website in BOTH the install and source versions of the DotNetNuke 4.9.0 framework. As the vb codefiles are "just in time" compiled each time the website application starts, you should be able to make (minor) changes in these files by opening the website in Visual Studio. However, the various entity and business controller classes for the Vendor/Banner functionality are part of the DNN library code that is compiled into the dotnetnuke.dll. For making modifications to these, you would indeed need to work with the source version, make the changes, and recompile the DotNetNuke libray. Depending on the scope of your modifications, you might also need to make modifications to the stored proceedures and tables relating to Vendors/Banners. Keep in mind that any changes made to the core framework will cause headaches when upgrading a non-standard DotNetNuke site in the future - particularly when upgrading to DNN 5.x.

The source for the Vendors/Banners code will be found in the Library/Components/Vendors folder of the version 4.9.4 source package which can be downloaded from the CodePlex site: http://dotnetnuke.codeplex.com/Releas....

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/27/2010 4:33 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

if you want to modify core modules like vendors/banners, copy all associated file into a new module solution, rename the namespaces and register it in DNN using a different name. this will prevent your changes from being overwritten on upgrades.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...Move a module from "Install" mode to "Source" to be able to modify.Move a module from "Install" mode to "Source" to be able to modify.


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