Is there a way to declare a dynamic component dependency on another component/module when that other component is a customized module that might not actually be installed in every environment — since a genuine dynamic dependency normally relies on referencing that other module's auto-generated `component_<modulename>_sys` package, which won't exist if the module isn't installed?

Q: Is there a way to declare a dynamic component dependency on another component/module when that other component is a customized module that might not actually be installed in every environment — since a genuine dynamic dependency normally relies on referencing that other module's auto-generated `component_ _sys` package, which won't exist if the module isn't installed?

Add the dynamic dependency explicitly in your own module's deploy.ini file, declaring the dependency from your module toward the possibly-not-installed customized module, rather than trying to directly reference that other module's generated package. The installer then generates the necessary dependency-handling package for you from that deploy.ini declaration regardless of whether the target customized module actually ends up installed in a given environment, correctly handling the conditional-dependency case.

Answer

Add the dynamic dependency explicitly in your own module's deploy.ini file, declaring the dependency from your module toward the possibly-not-installed customized module, rather than trying to directly reference that other module's generated package. The installer then generates the necessary dependency-handling package for you from that deploy.ini declaration regardless of whether the target customized module actually ends up installed in a given environment, correctly handling the conditional-dependency case.

← Browse Developer Studio, deployment, and upgrades questions