Hi,

this is an obsolete option, it was removed in 4.1.x MonoX version and obviously user manual is not updated. We will update the manual ASAP, thanks.

MonoX supports only fresh install and option to attach the new Web application to (new MonoX instance) to existing database, so can you please explain what exactly are you trying to accomplish, maybe I can provide you with additional information ?

Regards

I was curious to test how MonoX could be implemented at multiple levels of the same domain.
Example:
instance 1: domainname.com
instance 2: SubDomain1.domainname.com (indepentant CMS structure, but same membership info/db as root domain.)
instance 3: SubDomain2.domainname.com (indepentant CMS structure, but same membership info/db as root domain.)

I understand how to manipulate the providers, but installing all three instances to separate databases and then manipulating the membership providers still leaves the task of trying to keep users/roles synchronized between the three databases. It just seemed that the way it was worded in the user manual, the 'now removed' option sounded as though it had done exactly what I was wanting to test....maintain information on multiple installed instances, based on domain, and hopefully be able to simply specify whether they should share membership data or not(MojoPortal does this well).

Hi,

sorry for so late answer you can accomplish this by installing one MonoX instance and then direct all others to this instance (Do not use separate databases). Next step will be to insert new application records into aspnet_Application table and  change the web.config settings of all subsequent MonoX instances to point to separate application name. If this is an option for you we can provide you with membership provider changes that you need to implement so all of the MonoX instances points to same users and roles.

Let me know how do you want to proceed.

Regards