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...Administration ...Administration ...DNN and Source ControlDNN and Source Control
Previous
 
Next
New Post
10/16/2008 11:16 AM
 
Lampan

Joined: 3/9/2008
Posts: 6
Hi, I am searching solutions for following related to DNN and Source Control System. I am wondering how they could go hand in hand! I am curious to know how other are doing it... What is the process of development in DNN? Do you people ever do any modifications in DNN core? Have you ever felt the need to do so to accomplish something? If yes, How did you maintain the DNN versioning? If you ever modified in DNN core, how did you tackle it later while doing any upgradation in DNN? These may seem like a beginner's questions. I am indeed! Please share your valuable thoughts..! Thanks. Lampan.
 
New Post
10/16/2008 11:38 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

you should usually stand away from doing any modifications in the DNN core framework code - since all the functions are provided by modules. If you really need to modify core code, ensure, that it is well commented so you might be able to take changes over to next version before an upgrade.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/17/2008 12:59 AM
 
Lampan

Joined: 3/9/2008
Posts: 6

Thanks Sebastian! though.. A bit of confusion here! I am assumin all the Modules by default provided by DNN to be core code only. Is it correct assumption? I understand that Modules are available as separate download also. Do you mean to say that occasional changes in Modules are acceptable and okey, but no changes should be done in DNN core code other than any Modules. I am not sure if I interpreted you correctly. Please enlighten me.

Regards,

Lampan.

 
 
New Post
10/17/2008 8:03 AM
 
Alex Reinermann

www.icatt.nl
Joined: 10/9/2008
Posts: 12

Hi Lampan,

Here's how we go about this.

Within our Source Control System we have our main branche containing the sources we use as the base for our releases.
Next to it we created a development branche which we consider to be the development branche of the DotNetNuke Corporation.
When a new version of DotNetNuke is released by the DotNetNuke Corporation and we decide to adopt it, we update that specific development branche.
Next we merge this branche with our main branche.

When we decide to make adjustments to core code, something we try to do avoid as much as possible, we create our own development branche and make our adjustments in there.
After we are done with our adjustments we merge them back into the main branche.

If the DotNetNuke Corporation comes with a newer version and we decide to adopt it we update the development branche of the DotNetNuke Corporation and start merging again.

Hope this is enough information to get you started.
Else you can always contact me via our company website.

Regards,
Alex Reinermann

Alex Reinermann
Linked in		 Alex Reinermann - ICATT interactive media Microsoft Certified Professional Developer - Web Developer Microsoft Certified Technology Specialist - Web Developer - Distributed Applications
 
New Post
10/17/2008 1:21 PM
 
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

Lampan wrote
 

Thanks Sebastian! though.. A bit of confusion here! I am assumin all the Modules by default provided by DNN to be core code only. Is it correct assumption? I understand that Modules are available as separate download also. Do you mean to say that occasional changes in Modules are acceptable and okey, but no changes should be done in DNN core code other than any Modules. I am not sure if I interpreted you correctly. Please enlighten me.

Core Code is the framework itself, and IMHO you should stay away from changes as much as possible. Modules, bundled with the core are less critical and easier to modify. However, if you want to do major changes and be safe not to get your modifications overwritten on module upgrades, adopt name and namespaces and use custom database objects, like gammacon did, when we created gammacon.UDT as enhanced version of UDT 3.1 (and the seed for UDT 3.2 and later enhancements).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN and Source ControlDNN and Source Control


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