Visual Data's JumpStart DNN creates a DotNetNuke installable PA for every table that you define in the DatabaseBuilder.
This is a zipped file that contains all the nessesary codefiles that DNN needs to install and register your module.
A typically set of PA contains the following codefiles:
Name File Size
-------------------------------------------------------------------------
VDW_JS_03_JSMyJumpStart_View.ascx.resx 9,370 KB
VDW_JS_03_JSMyJumpStart_Edit.ascx.resx 23,779 KB
Settings.ascx.resx 12,120 KB
Name File Size
-------------------------------------------------------------------------
VDW_JS_03_JSMyJumpStart_View.ascx 105,012 KB
VDW_JS_03_JSMyJumpStart_Edit.ascx 38,585 KB
Settings.ascx 9,384 KB
Name File Size
-------------------------------------------------------------------------
VisualData.VDW_JS_03_JSMyJumpStart.dnn 4,379 KB
Name File Size
-------------------------------------------------------------------------
module.css 0,735 KB
Name File Size
-------------------------------------------------------------------------
01.00.00.SQLDataProvider 16,615 KB
Uninstall.SQLDataProvider 2,581 KB
Name File Size
-------------------------------------------------------------------------
VDW_JS_03_JSMyJumpStart_Controller.vb 11,417 KB
DataProvider.vb 4,068 KB
VDW_JS_03_JSMyJumpStart_Info.vb 27,404 KB
SQLDataProvider.vb 12,184 KB
VDW_JS_03_JSMyJumpStart_View.ascx.vb 342,715 KB
VDW_JS_03_JSMyJumpStart_Edit.ascx.vb 187,709 KB
Settings.ascx.vb 5,652 KB
-------------------------------------------------------------------------
|
|
How to handle your modules when updating?
DotNetNuke's PA installation routine lets you install new modules, obviously ;)
But it lets you also update existing modules.
What is the difference, and how to handle when installing or updating your modules?
The main diffence between installing and updating is that DotNetNuke will run the SQLDataProvider when you INSTALL a NEW module, thus also installing the associated table and stored procedures in the database.
When UPDATING an existing module, DotNetNuke wil only copy the code to the DNN app_code and desktop directories.
So, when you need to update an existing module in wich you have altered the DATABASE, you must force DotNetNuke to uninstall the existing database table and stored procedures. This is done when you UNINSTALL the module prior to re-install the upgrade version.
This will DESTROY the existing data in the table, however!
One option to prevent the loss of data is to export this data to an Excelsheet first, and restore the data in the upgraded module with the EXCELReader function.
|