1 person found this helpful
Not trying to dissuade you from your approach here, but it's something to consider.
Several years ago I did some work for an employer that also offered software that worked much as you describe. The help system was antiquated and they were in the process of bringing it into the Windows platform from being DOS based. I described to the owner of the company that we could fashion the help so they only had help for what was installed. His response was eye opening for me.
NO, I want the customer to always have ALL the help as if they had purchased every module. By seeing the help and what is possible to achieve with other modules, perhaps it would entice them to later purchase the additional modules!
Something to consider. It certainly made me think differently about this aspect... Rick
Helpful and Handy Links
Thanks. That is helpful, but if I understand it correctly the help other(me) has to add or remove child projects as required.
Do you know of any way for the on/off switch in application code to expose/hide the child project?
Thanks, we will probably do that when the new features are actually available. For the moment they are turned off and the help topics need to be "off" too.