Is any detailed documentation yet available (other than Charles Nurse's blogs) on the structure and new features of the version 5.0 package manifest file?

I noticed that all module packages included with DNN 5 RC2 use the version 3.0 manifests. I was hoping that some of these might have been converted to the new extension installer manifest to serve as examples of the new structure. What is the plan for releasing upgrades of core module packages - keep most compatible with DNN 4 and use version 3.0 manifest structure for now?

Am I correct that for a module developer to make use of the new installer capabilities (such as the manifest nodes for owner, license, releasenotes) for DNN 5 and still offer a module package for DNN 4, it will be necessary to provide two separate module packages - one for DNN 4 with the version 3.0 manifest and one for DNN 5 witht he version 5.0 manifest? Or, will it be possible to provide only one packages containing both manifest files?

Will the use of the < resourcefile > node be still supported in the version 5.0 manifest?

---

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

This would be very useful. Even bettter might be if some of the avaliable XML nodes were would work with the existing manifest version.

 

For example (taken from Charles blog):

• owner - the owner of the package
  • name - the name of the owner
  • organization - the organization that owns/created the package
  • url - A url to the owner's website
  • email - A support email address for communicating with the owner
• license - the license for the package - the license text can either be embedded in the manifest - or in an external file
  • src - the location of the license text - if in an external file
• releaseNotes - release Notes for this version of the package (as with the license the text can be embedded in the manifest - or in an external file)
  • src - the location of the release notes - if in an external file

It would be beneficial if these could be added to existing manifest files so that the same DNN installation file could be used for both DNN 4 and DNN 5 installations. Of course, this really wouldn't push developers to move towards the new manifest, but it would be greatly beneficial as users migrate to DNN 5 if they could have one installation file.

 

Or maybe it is? When I was testing some test installation files I tried adding these nodes just under the module description, business controller class, etc... and they didn't appear (such as all of the owner information) during the installation process.

 

 

-Chad

www.datasprings.com