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...Building ExtensionsBuilding ExtensionsModulesModulesBest Practice for Updating a ModuleBest Practice for Updating a Module
Previous
 
Next
New Post
2/6/2012 12:46 PM
 

Hi,

I'm working on a DNN portal that has a few custom modules installed.  I need to change the programming logic of some of them.  What are the steps for updating a module already installed on a portal? 

Thanks,

Sid

 
New Post
2/6/2012 9:58 PM
 
Hi Sid,
As you said you need to change the programming code, so first, you need to get the source code of this module, then update the code using a IDE. When complete the changing, you need to repackage this module and reinstall it. Remember to increace its version number to a higher one than current.
Above is the common method. For a simpler one, you can just copy the new .dll file of this module to the bin folder of the website. this is not recommended.

NovaSoftware ---a professional outsourcing company in China .
* More than 6 years' offshore experience in DNN
* Successfully developed 30+ websites , 250+ DNN modules, 50+ sets of Skins/Containers.
* Demo Site:http://dotnetnuke.novasoftware.com/
 
New Post
2/7/2012 2:52 AM
 
Eileen Zhang wrote:
Hi Sid,
As you said you need to change the programming code, so first, you need to get the source code of this module, then update the code using a IDE. When complete the changing, you need to repackage this module and reinstall it. Remember to increace its version number to a higher one than current.
Above is the common method. For a simpler one, you can just copy the new .dll file of this module to the bin folder of the website. this is not recommended.

 Hi Eileen,

I retrieved the source via FTP.  I copied it to c:\dnn563source\website\desktopmodules\myregistrationmodule.  I then created a new DNN Module project in VS 2008 and added those files to it.  When I build, I'm getting tons of errors.  I noticed that the .ascx Inherits statement refernces something different than my solution's namespace.  Can I safely change that?  Or, is there a better/easier way to do all of this?

Thanks,

Sid

 
New Post
2/12/2012 9:31 PM
 
you can change your solution's namespace and make them the same as the .ascx inherits.

NovaSoftware ---a professional outsourcing company in China .
* More than 6 years' offshore experience in DNN
* Successfully developed 30+ websites , 250+ DNN modules, 50+ sets of Skins/Containers.
* Demo Site:http://dotnetnuke.novasoftware.com/
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesBest Practice for Updating a ModuleBest Practice for Updating a Module


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