OpenDCL 8.0.5.0 doesn't seem to register properly in 2017
OpenDCL — modern dialog UI for AutoLISP.
Brought to you by:
owenwengerd
Menu
▾
▴
#784 OpenDCL 8.0.5.0 doesn't seem to register properly in 2017
Hello, OpenDCL 8.0.5.0 doesn't seem to register OpenDCL command properly. Have installes Infrstructure Design Suite Ultimate 2016 and 2017 on the same machine. It works on 2016 but not on 2017. Even when I added the reg keys manually, the command appears in the suggestion list but is obviously not available (unknown command).
Regards, Fred
Discussion
The behavior you describe indicates that something prevents the runtime from loading successfully. I could not reproduce this on a Windows 7 x64 machine. Here, OpenDCL Runtime loads as expected in plain AutoCAD 2017.
Does the path in the demand-load registry key OpenDCL\Loader match the actual installed path of the file? Make sure you consider which user account your AutoCAD is running under. For example, mapped drives may not be mapped the same when running under a different user account.
If the path is correct, and the .arx file loads manually, then I wonder if there is some setting related to trusted folders that prevents the OpenDCL Runtime from loading.
Please let me know if you uncover anything new.
Last edit: Owen Wengerd 2016-07-02
You might try to run the installer as an Administrator to see if it makes any difference. Normally the installer runs as a restricted user with elevated privileges, which causes the demand load registry keys to be written to HKCU. If you run the MSI from an elevated command prompt (i.e. start a command prompt 'as Administrator'), for example, the setup code will write demand load registry keys to HKLM, making them available for all users on the machine. This would rule out permissions issues causing the demand load to fail.