Last post May 26, 2005 11:42 AM by ErikVB
May 25, 2005 06:49 AM|Robbie|LINK
May 25, 2005 07:15 AM|SamTanner|LINK
Most module upgrades are performed by uploading/installing a PA, just like an original module installation. The author will include upgrade scripts to make any necessary changes to the database.
The module's source .dll is placed in the main /bin directory by the installer program, replacing the previous version.
May 25, 2005 08:14 AM|Robbie|LINK
thanks sam I didnt expect it be so straight foward.
May 26, 2005 02:39 AM|pblanton|LINK
May 26, 2005 04:00 AM|anthony.glenwright|LINK
May 26, 2005 04:11 AM|pblanton|LINK
May 26, 2005 05:28 AM|ErikVB|LINK
The developers who really care use our DNNUpdate service :-)
May 26, 2005 07:08 AM|anthony.glenwright|LINK
May 26, 2005 10:13 AM|Revlis|LINK
May 26, 2005 11:31 AM|pblanton|LINK
May 26, 2005 11:42 AM|ErikVB|LINK
The sql script of a module is only executed if the version of the script is higher than the current installed version in the database. So if a user installs a module for the second time, the files will be copied, but the sql script won't be executed (unless
you manually change the version number in the database first) .... so this is quite a safe way to work. Further more, the codesmith templates only generate stored proc scripts, and ofcourse it is of no consequence if you delete the sproc first and create it
later ... you will never loose data this way. The create script of the table is courtesy of the developer .... and its quite bad practice to just drop a table in an upgrade script ...