The bad news:
As of February 20, 2009, ASPDNSF ML/DNN version 7.1.2 will not work with DotNetNuke 4.9.1+ in a production environment. A new version will be required to operate with existing production systems and multiple portal installations.
The good news:
Many of the issues are known and resolvable.
The side effects:
ASPDNSF ML/DNN advertising should suspended immediately from dotnetnuke.com until the product meets the DotNetNuke Module Review Fundamental Requirements or the following minimum criteria:
1. Install without error
i. Do not break existing web configurations
ii. Adequate and accurate documentation for install/upgrade
2. Uninstall correctly
i. Do not break existing web configurations
3. Support Virtual Portals
i. Remove the requirement for Portal 0
ii. Module.Portal ID for all read/write file access including anonymous and users
iii. Concurrent users or content editors (document premium module setting)
4. Error handling including informative error reporting
i. Request DNN before module initialization
ii. Verify actual portal id vs. assumed portal id
iii. Implement try/catch for XML package processing (and know when it fails)
IMHO, based upon my recent efforts, using SWAG (Scientific Wild Ass Guessing) ML/DNN seems to work only with a single user on an empty DNN site.
ML/DNN currently requires extensive knowledge of DotNetNuke and ASPDNSF to make it work in a production environment, which may explain why there are so few known production sites.
On the other hand, there are only a few minor issues to resolve to turn this into a viable product.