How to Create a Module Install Package (Basic)

These instructions

  1. cover creating a basic Install Package for DotNetNuke version 05.06.03 (45).  Stay tuned for updates on more complex installs.
  2. assume that you have successfully manually installed your module and that the App_Code and DesktopModules folders contain all the required files.  Required files change based on the complexity of your module.  For example if there is no back end database to your module you will likely not need the App_Code folder and you definitely won’t need the version.SqlDataProvider, or uninstall.SqlDataProvider files.

Once your custom module has been successfully installed on your Dot Net Nuke site:

1. Log in as “Host” and click on “Extensions” in host menu

To select the extension, click on the pencil icon next to it in the list of extensions.

At the bottom of the page click the Create Package link.

 

2. The Create Package screen (shown below) will present the information you have already entered for Name, Type, Friendly Name, and Version.  Below that leave the “Use Existing Manifest” unchecked, as we will be creating a new manifest.  Make sure “Review Manifest” is checked.  If everything looks good, click “Next”.

3. The file selection page should be automatically filled in, but check the list to make sure no files were missed.  Leave the “Include Source” unchecked.  If everything looks good, click “Next”.

4. Assemblies are not covered in these instructions because a basic install would likely not include any assemblies.  Leave the box blank and click “Next”.

5. Reviewing the manifest.  The manifest should all ready be filled in for you since DotNetNuke creates the manifest.  If this page is blanked something went wrong and you’ll need to start over.  If it’s not blank simply review it to see how it’s built.  This will help get you familiar with the manifest when creating more complex packages.  If everything looks okay, click “Next”.

6. Create Package.  This page will also be filled in for you.  While it is possible to alter, or shorten, the Manifest and Archive file name there is no need outside of aesthetics and naming convention.  For now, leave them as is and click “Next”.

7. At this point the package will be created.  The listing will show all the steps that were completed and if there are any errors they will show up in red.  If there are no errors you can find your package in your DotNetNuke installation in the Rootinstallmodule folder.

8. To test your install download the package and simply install it on a DotNetNuke installed of equal or greater version.  Note that your package will like only be compatible with whatever version of DotNetNuke you use to create your install package.

1 comment for “How to Create a Module Install Package (Basic)

Leave a Reply

Your email address will not be published.