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.0What are the DNN Core Code?What are the DNN Core Code?
Previous
 
Next
New Post
10/15/2008 11:51 AM
 

yy wrote

If I want to slightly alter how a user control under the Website/admin folder work, can I just make the changes to the control or should I create a new user control?

Also where are the source code for the Modules? for example, under Website/DesktopModules/Blog/Blog.ascx, it has page derective like  Inherits="DotNetNuke.Modules.Blog.Blog", but where can I find its code behind?

If you want to change a control that comes with DNN (for example, in the admin folder) you should create a new copy of that control, rather than altering the control itself.

The source for specific modules are available on those modules pages, which eventually takes you to the DNN SourceForge site, where all of the source lives.

Hope that helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
10/15/2008 1:55 PM
 

Brian Dukes wrote

If you want to change a control that comes with DNN (for example, in the admin folder) you should create a new copy of that control, rather than altering the control itself.

The source for specific modules are available on those modules pages, which eventually takes you to the DNN SourceForge site, where all of the source lives.

Hope that helps,

That's exactly what I was looking for. Thank you very much Brian!

I think now I totally got the idea that I should create my own copy of the controls even if it's only a slight alternation so there will be no problems for the upgrades later.

Still one more question about the controls in the Admin folder, if I create a new copy of the Login.ascx controls there, that means I need to compile the DNN solution to see the changes I made on the control. But I read in the answers to another of my posts that DNN solution don't need to be compiled. Will the compilation affect the portal site in anyway? Also where does the controls under the Admin folder compiled to? What's their dll? thanks!

 
New Post
10/15/2008 2:43 PM
 

The controls in the /admin folder are compiled dynamically, just by having their source included in the website.  There is no permanent .dll in the bin folder for those controls.  In contrast, the code behind of the controls in the /controls folder are compiled into the DotNetNuke.dll (the library project in the source package).

All you would need to do to create a copy of the login control is to copy its control, codebehind file, and resx file (from the App_LocalResources folder).  You'll, as mentioned, rename the namespaces, and make your alterations.  In order to get DNN to use that new control, change the ControlSrc column in the ModuleControls table where it points to the standard control to point to the new one.

Hope that helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
10/15/2008 5:43 PM
 

Brian Dukes wrote
 

The controls in the /admin folder are compiled dynamically, just by having their source included in the website.  There is no permanent .dll in the bin folder for those controls.  In contrast, the code behind of the controls in the /controls folder are compiled into the DotNetNuke.dll (the library project in the source package).

All you would need to do to create a copy of the login control is to copy its control, codebehind file, and resx file (from the App_LocalResources folder).  You'll, as mentioned, rename the namespaces, and make your alterations.  In order to get DNN to use that new control, change the ControlSrc column in the ModuleControls table where it points to the standard control to point to the new one.

Hope that helps,

Thank you very much, Brian! It's very helpful. I feel I have a good direction to start now.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0What are the DNN Core Code?What are the DNN Core 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