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.0Universal Package InstallerUniversal Package Installer
Previous
 
Next
New Post
1/10/2008 10:57 AM
 

A couple of DNN point versions ago I noticed the appearance in the framework's Install/Package folder and in the installer source code references to a universal "Package" as a means of installing non-module, non-skin/container elements.  A forum search turned up this thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/190820/scope/posts/Default.aspx

As I am looking into the best way to package the image upload and editing control that I've been building for distrubution, it would appear that the new universal package installer would be the way to go. The distribution will need to include several dll's, a generic http handler (ashx) and a webservice (asmx). In addition, should file based cacheing of the working image be selected rather than or in addition to memory based cacheing, a folder will have to be added at the portal level and a custom scheduled task (to clear the file based image cache) be installed.

Has there been any further decisions and/or work on opening up the universal package installer for non-core use, freezing its API and features and any documentation produced with respect to the manifest file of a package? Has anyone done any non-core work with the installer, particularly in defining new package types?


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/10/2008 7:16 PM
 

William, the answer Charles gave in that thread is still valid. He is working on extending the installer to support more types. The first Cambrium / dnn 5.0 will have a much more complete installer.

Right now you would have to resort to a dummy module installer


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

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

 
New Post
1/10/2008 10:31 PM
 

Thanks Erik - I thought that would be the case. The package installer will be a welcome addition for such add-ins.  I've used the dummy module route before and will this time as well - just seems a bit of a hack. Fortunately I'm using a generic http handler so don't need to make changes to web.config.


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
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Universal Package InstallerUniversal Package Installer


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