autodesk/migration/inventory/plant3d-2019/launcher-analysis.md

Launcher analysis

Confirmed from source

• Project: \\phpsrv03\NBIM\code\CS\All_Serv_Load\All_Serv_Load\All_Serv_Load\All_Serv_Load.csproj, lines 5–16: WinExe, assembly All_Serv_Load, target .NET Framework 4.8, AnyCPU, output bin\Debug/bin\Release.
• Entry point: Program.cs contains the WinForms startup; Form1.cs is the operational UI.
• Settings: F1_Xml.cs:78–81 deserializes Settings.xml from the process working directory. Form1.cs:45–56 loads and validates it.
• Plugin list: Form1.cs:136–175 opens download_list.xml, validates XML and calls the copy/validation path.
• Copy/update: Form1.cs:251–392 checks help/source/target/loader paths, removes stale files/directories and copies plugin catalogs/files; Form1.cs:404–526 recursively copies directories.
• Process launch: Form1.cs:198–205 starts the configured object and passes the selected project path as an argument. The exact production object depends on Settings.xml and was not executed.
• Plant startup: All_Serv_Load\All_Serv_Load\Addins\start_plant_3d.bat:4–8 starts C:\AutoCAD User Support\p3d-support\PlantCleaner.exe, deletes %appdata%\Autodesk\PnPPersistentCache\*.*, then starts C:\Program Files\Autodesk\AutoCAD 2019\acad.exe /product PLNT3D /language "ru-RU".

Not confirmed

No source evidence was found in the inspected Launcher files for /p, /w, /t, registry writes, shortcut creation, NETLOAD/ARXLOAD/APPLOAD, bundle registration, licensing or runtime version checking. Settings.xml, downloaded lists and the ZIP packages need a separate content review without execution.

Static load behavior

The Launcher is a file distribution and process-starting layer. AutoCAD/Plant 3D itself and app_netload.lsp-style support files load the managed DLL family. Several plugin sources reference C:\AutoCAD User Support\Applications\app_netload.lsp; those references are recorded in hardcoded-paths.csv and load-search.csv.