I have some modules and am at the point where they are being used, but still under significant extension.  So I am constantly rebuilding the with new functionality and need to install them in the test site.  When I add control, or change some parameter which is reflected in the dnn file, I always have to uninstall the currently running verion and then install the new version.

Naturally, when this happens I then have to go back to the pages where the module was installed and add them back in.  This will eventually be hundreds of pages and so I am worried about the long term maintenance implications.  I have read about the upgradable interface but don't have to execute any logic on update.  Also, can't really figure out what it does or where it is to be implemented.  And I don't know if it addresses this isse.

I don't package the controls up.  This is all internal so I just replace the code and desktop module folders at the site.

What is the proper solution to this situation?

Jeff Landry

You got a good solution for your problem. As mentioned by lolocmwa you need to keep the every version of your module.

In addition if change the script files then you can increase the module version number. But if you do not change the DB script then you can install your newly developed module without creating any version.

What DNN Module Install engine will do: It will check your existing module definition if module version is same then engine will not execute the script files but it will update your module directory.

Now you can think what you want to do.

No, you do not need to remove the currently installed module.

If you install the same version of the module then your control files will be updated by the module install engine.