The current manifest allows to delete files during uninstall. Is there a way to perform a more complex clean up (e.g. moving files) through the manifest or subscribing to some uninstall event? The IUpgradeable event doesn't seem to notify on uninstalling.

Thanks,

---

Try our powerful shopping cart module for DotNetNuke!

Thank you for the confirmation. I have voted !

Does anyone know a workaround?

---

Try our powerful shopping cart module for DotNetNuke!

I think the whole module install/uninstall/package thing could benefit from a review.

There are dozens of places where you need to update the version number manually, which can be tricky when you include multiple modules in one package, skins use zip files inside zipfiles and you need to specify manually which files should be deleten on an uninstall.
It all seems unnecessarily complicated.

I've looked into the install/upgrade procedure today and think it has some quirks. For example that you can supply a list of files to be deleted (and only deleted) after running a database script, using a file named .txt. If there is no database update script included, you can't delete files and if you want to rename/move files, you have to do it programatically.
Also the database-update is run only once, while the UpgradeModule method is also run when you reinstall a module.
(well... you hope it is run, because this blogpost might cause some concern: http://www.dotnetnuke.com/Resources/B.... It's form 2005, but I can't find whether it has been fixed (maybe it's in the 12 comments which I also cant find))

Also you can reinstall a module that is already installed, but you can not downgrade a module. I had to uninstall it completely, which removed the module from all sites and pages. And after that I couldn't activiate the module because the old (uninstalled) instance still had the license key registered to it. (Both of which were (down)time consuming problems recently when an update from some third party module which should have been a tiny bugfix, introduced a much larger bug.) The thing I unfortunatly learned from this was to only increase the version number when a downgrade would be impossible, otherwise just release with the same version number to allow for downgrades.

I wonder what weird things will show up more on the uninstallation process.



The mentioned "systemwide events model" could at least enable a module to unregister itself at a licensing server, but it doesn't sound like a small feature at all (and having worked with messaging systems I know it is very nice to have, but can be a very complex thing)