Skip to content

Deploying a module in Developer Studio fails because a utility package compiles before the entity view it depends on, and `deploy.ini` settings like `CapMergeFiles`/`CapMergeFilesLast` don't seem to change that.

Answer

Deploy ordering can only be controlled within a single file extension (for example, forcing one .apv file ahead of the rest of the .apv files) — it can't reorder deployment across different file extensions, so a dependency between an entity's view and a utility's package (different extensions) can't be fixed this way; restructure the dependency (or split the utility so its dependent piece deploys in a later extension pass) instead of trying to force cross-extension ordering.

← Browse Developer Studio, deployment, and upgrades questions