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.0iUpgradeable- how to?iUpgradeable- how to?
Previous
 
Next
New Post
2/5/2008 12:02 PM
 

I'm finding it a burden to support the modules I've built on my customer and my sites because I do these upgrades by hand and now really must find out how to implement iUpgradeable properly. While I accept and understand that some of the documentation is not good, there is a distinct lack of a comprehensive site or doc to describe the upgradeable capabilities of DNN.  Clearly it works since many modules and the DNN Core do it- does anyone know how to do it?  What I want to be able to do:

  • Package a version-controlled dnn module.  I know how to set up the .dnn file but what about how to remove and install files and scripts that change form version to version (the xxx.yyy.zzz.txt file?)
  • Set up the 'new version available' image on the module definitions summary page.  The DNN Project modules can do this- is this capability reserved only for the DNN project modules, or is there a way to this myself for my modules?

 I've searched everywhere and although I can find a piece or a reference here and there, there's nothing definitive that fills me with confidence.

 

 
New Post
5/22/2008 9:54 AM
 

I will have to agree with you. I am in the same situation and am having a hard time trying to find a workable sample to reference. If I find anything, I will re-post here.

 
New Post
10/17/2008 4:35 AM
 

Any news on this?

I'm struggeling with a hand-made package 'composer', because the DNN 'create package' includes too much of not-needed files and too little of required files (like dll's). When I want to upgrade my module, I still have to uninstall and re-install the module. This causes the module to disappear in the page(s), so I also need to manually insert the module again on every page.

Please let me know if I'm missing something here, because this method is really time consuming.

Thanks in advance!

 
New Post
10/17/2008 5:40 AM
 

remember to increase the version number of the module in the module manifest (.dnn file). DNN Uses this version to run new sqlprovider scripts (if there are any)

other than that there should be no issues installing a new version of a module ontop of an existing one. Can you be more specific about the issues you get?


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/5/2009 3:25 PM
 

Hi EricVB,

Maybe, this is off-topic, but I will tell my story about my upgrading issues (with DNN 4.8.2) here.

1 Creating the package with DNN does not include all (or even any?) referenced dll files.
2 Creating the package with DNN does not include all dll files in the .dnn file.
3 Upgrading a modules throws a database error (I believe it tries to insert the module(definition?), but it already exists)

I have not used the 'create package' and 'upgrade' functionality for a while now, so please forgive me if I leave out the details.

Kind regards,

Willem

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0iUpgradeable- how to?iUpgradeable- how to?


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