We have a daily build that build new set of custom modules with same version number and auto deploy to QA environment. When we do release or service pack, we will then increase the version number. However, this does not work in current DNN implementation. (we used to have our custom installer  in 4.9.X but not able to make PAInstaller work in DNN 5.X.X). In another thread, I guess it’s recommended to use extension installer in 5. By doing so, extension install will run only if it’s new version. Is it possible to run on the same version? Basically, I want it to re-run on the same version.

Even if we increase our version number daily, the max that it can support is 99 which is a problem. Any suggestion or workaround for this issue?  

I would prefer to get PAInstaller to work but not able to locate the code in DNN 5.

The extensions installer in DNN 5.x will allow you to do a "repair" installation after checking the "Repair" checkbox that appears after you start the install of an extension of the same version. Provided that your SQL scripts, any "run once" code such as in an implementation of IUpgradable, and module/module control registration has not changed or been added to, the repair option can be a good way to update the extension's assemblies and user controls.

It would be ideal if the installer could be extended look at the revision field of the version as well as the major-minor-build fields.

Another approach that I've been experimenting with is to place the development project and all code outside of the usual DesktopModules/MyModule folder then use a custom build task to "deploy" the assemby(ies), controls, etc. to the test/debugging website. Updating SQL objects is still a problem unless one does incremental scripts then merges changes back into one script for the release version. The downside of development outside of the DNN website seems to be some problems with resolution of the various DNN user controls for intellesense and occasional failure of the .designer file update following changes to its corresponding .ascx control.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner