Archive
Monthly
Go
|
|
DNN Blog
Mar
26
Posted by:
Charles Nurse
3/26/2008
As a result of my previous Blog on the Features Module (Cambrian First Look - New Features Module (Pt 3)) I recieved a couple of suggestions on improving the "Package Writer".
- The new Package Writer auto-generates file lists for inclusion in the package BUT adds the opportunity to edit the list. It would be useful to be able to do the same with the generated manifest, prior to it being added to the package.
- While the new Package Writer provides much more flexibility to the developer in packaging their module, it does this by implementing a multi-step Wizard. If you are just repackaging a module because you made a simple change in one file, you do not really want to go through the multi-step process I showed before.
To respond to the first suggestion, I have added a new Wizard Step - which displays the Manifest generated from the Package Information and the file-lists. The user now has the chance to edit the manifest before clicking the "Next" button.
To respond to the second suggestion, I have added two check boxes to the "first page" of the Wizard.
The first check-box allows the developer to use the existing Manifest (this is saved in the database). If checked the pages that allow the user to edit the files in the package and the assemblies in the package are skipped. If the Review Manifest box is checked the user can still review the Manifest (above), but if the Review Manifest box is unchecked the user goes to the last page to complete the creation of the package.
4 comment(s) so far...
Re: Cambrian First Look - New Features Module (Pt 3) - update
Looks great! Will there be any support for shared assemblies? So if 3 modules install ajaxcontroltoolkit.dll and the user un-installs 1 module, the other 2 won't break. It would also be nice to be able to include scheduler tasks in the manifest also.
Thanks,
Mike
By digmike on
3/26/2008
|
Re: Cambrian First Look - New Features Module (Pt 3) - update
Yes digmike - that is already included, including versioning of shared assemblies. Thus if module A installs v1 of shared assembly, and module B has v2 - module B's will overrwrite. If module B is installed first, then module A's shared assembly (v1) will NOT overwrite module B's v2.
By cnurse on
3/27/2008
|
Re: Cambrian First Look - New Features Module (Pt 3) - update
Charles, that is great news! It would be great if we could include 2 manifests in the same package. One that installs pre-5, and one for 5 and above. Thanks, Mike
By digmike on
3/28/2008
|
Re: Cambrian First Look - New Features Module (Pt 3) - update
I agree with mike, furthermore, I believe if the installer can support multi-packages with different type(module/skin/provider) at the same time, we can create more complex application ,not only one module. At least, we can install one skin package with the skin and its container package just one time.
James
By koy2000@sina.com on
7/18/2008
|
|