morozovsa/autodesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

audit: inventory Plant 3D 2019 launcher and plugins

Browse Source
This commit is contained in:
codex
2026-07-30 10:25:30 +03:00
commit 694da5657e
19 changed files with 12297 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
migration/inventory/plant3d-2019/migration-risks.md
+11
View File
@@ -0,0 +1,11 @@
# Migration risks
1. **Version-coupled Autodesk paths.** Many project references and debug start programs hard-code `C:\Program Files\Autodesk\AutoCAD 2019` and `PLNT3D`; the BAT hard-codes `acad.exe` and `p3d-support`.
2. **API surface breadth.** Projects use both AutoCAD/ObjectARX managed APIs and Plant 3D ProcessPower/PnP APIs, including ortho DBX/UI assemblies. Compatibility with 2026 is unknown and intentionally not inferred.
3. **Deployment order and cleanup.** Launcher code deletes/replaces target plugin directories and copies catalogs recursively; partial network availability can produce incomplete installations.
4. **Duplicate lineage.** The source tree contains versions, archives, releases and copied DLLs, so “the” production build input is not yet uniquely identified.
5. **Unresolved runtime loader.** Static evidence points to support LISP and command registrations, but the effective startup suite/support path and deployed download list were not runtime-confirmed.
6. **External resources.** UNC shares, mapped drives, `AutoCAD User Support`, template/project paths and external DLL folders appear in source/configuration.
7. **Credential review.** Password/connection-string keywords exist; values are omitted and require controlled secret review before migration.
No risk statement here is a compatibility verdict. Each is a migration investigation item based on static evidence.