{GoogleHorizontalTextScript}
Attention developers! DotNetNuke 5.0 Cambrian has a nifty new tool to help developers package their modules nicely to fit with the new “Extensions” manager. Under the old Module Definitions manager, which is now the Extensions Manager, you can still create and edit Extensions (Module Definition) Settings, but now there is additionally a “Package Settings” section as well.
Check out this nice tool…Fill in all the information for your custom module package and click on Create Package
Then, on the next screen you will be able to finalize your package by either reviewing your DNN Manifest file or accepting the file as is
Let’s select "Review Manifest” – This brings up a list of files in the module folder. However, the package writer states that I can add and delete files as well as choose to include the source code. As you can see in the image below, there is no “Include Source” checkbox…so I’m not quite sure what to make of this yet. I’m going to accept the files as they are now and click Next.
On the next screen, Choose Assemblies to Include, you can add and delete assembly files to package up with your module. However, while I didn’t have any assemblies to package in this scneario, I couldn’t find how I would have added them if I had wanted to. Hmmm….. Next.
Alright, now here we are on the Create Manifest screen where you can see the output from the Package Writer. On this screen, you can hand edit any thing you may need to before hitting Next
On the Create Package screen, you have some options regarding the output packaging of your module.
The Create Manifest File check mark will place a copy of the manifest file in to the module folder named with your entry in the Manifest File Name textbox. Whether you choose this option or not, an entry will be placed in the database for this module. You can find the record entry in the Packages table of the DNN Database.
To create a zipped up module package, check Create Package and use the Archive File Name text box to name the package. Note that this will be the actual name of the zip file that you want to create, DotNetNuke is not going to name it for you, such as with version numbers, as in previous DNN versions. Also, don’t forget to add the “.zip” to the end of your archive file name.
Click Next when you’ve filled in the information and go to the Create Package Results screen as seen below.
Finally, one more thing worth mentioning is that unlike prior DNN versions which placed your module package in the Install\Modules folder, you will find your module in the root of the host portal’s folders:
And that’s it. When I figure out what’s going on with the add/delete files and assemblies screens, I’ll update the article. In the meantime, it’s still a useful tool and it’s easy enough to modify by hand to work around those for now.
{GoogleXLargeImageVE}