Files
autodesk/migration/audits/p-rec-annot-legacy-loading/legacy-vs-new-loading.md
T

1.9 KiB

Legacy versus new loading model

Legacy behavior Legacy evidence New implementation Compatibility requirement Decision Risk
Unknown external bootstrap loads OrthoLoader.dll loading-chain.md Bundle bootstrap not selected yet Identify the workstation/project startup owner first Defer loading-model decision High
20 independent DLLs loaded in order Settings.xml, Loader.cs:63-81 one entry assembly currently Preserve required command availability, not the DLL count Evaluate command/module migration individually Medium
DLLs loaded from OrthoLoader's directory (possibly UNC) Loader.cs:49,65; bootstrap source unknown local smoke bundle only Decide offline/update policy with operations owner Do not hard-code UNC in new code High
Settings.xml controls order Loader.cs:104-112 MSBuild/bundle manifest currently Preserve explicit dependency ordering where behavior requires it Document, do not emulate blindly Medium
central PluginsOrtho Ribbon Ribbon.cs new Promhimproekt tab Preserve actual command mapping where adopted Separate UI migration decision Medium
project selection uses local app_netload.lsp Ribbon.cs:380-405 no equivalent Confirm security/project-selection policy Do not reproduce hidden local control file High
network icons and documents Ribbon.cs:330-357, deployed files bundle resources Bundle only licensed, necessary resources Replace network runtime dependency Medium

Recommendation: do not choose AppLoader or a manual-NETLOAD model yet. First identify the missing external bootstrap and confirm whether app_netload.lsp is the corporate launcher contract. Once confirmed, use a single versioned entry assembly with explicit manifest/dependency validation; avoid sequential programmatic NETLOAD and UNC execution because the legacy chain is non-atomic and fails the remaining modules after one error.