Author Topic: Upgrading an OpenDCL runtime installation when AutoCAd is upgraded by the user  (Read 5235 times)


  • Member
  • *
  • Posts: 27

For example, suppose I have OpenDCL Runtime 8.xx installed when the latest AutoCAD version on the machine is ACAD 2014.
The ODCL runtime version for this product is evidently OpenDCL.x64.19.arx, which is the latest ODCL version installed by the ODCL Runtime msi (or msm). ODCL website says there is (tentative) support for AutoCAD 2015, which presumably means there is an OPenDCL.x64.20.arx which was not installed, due to ACAD 2015 not being present at the time of the ODCL Runtime install. Is this correct?

Fine and dandy. I assume I can rerun the installer and have it detect ACAD 2015, then install OPenDCL.x64.20.arx.
Is this correct? (I have not simply tried it - please read on).

My question is:
Suppose I distribute a project using ODCL, & user's situation is as described above.
AutoCAD will migrate the LISP files & all other such as part of the upgrade.
So, the user now has some "dead" add-ons until the ODCL Runtime is upgraded for their new ACAD.
How to instruct the user?

Q: IF I create an installer using the ODCL msm, should/can the user rerun my installer to install the latest version of the ODCL Runtime? This seems clunky, to me.
I have no experience creating installers, so i have no idea if this makes any sense, but would like to try my hand at it, so am looking for information which might eliminate future problems...TIA


  • Administrator
  • Hero Member
  • *****
  • Posts: 3059
    • Outside The Box
Your thinking is basically correct. When installing OpenDCL Runtime, the .arx modules are always installed even for unavailable versions of AutoCAD, but the demand-load registry keys are not created unless the associated AutoCAD version registry key already exists.

Users should not be "migrating lisp files" to new versions of AutoCAD unless the lisp files are their own files and they know what they're doing. Obviously lisp files are generally easier for users to manage on their own, but if they are sophisticated enough to port third party applications, then they have to be responsible for the consequences or figure out on their own that they also need to update OpenDCL Runtime.

The bottom line is that you should create your own installer, and end users should get updates from you when new versions of AutoCAD are released.

BTW, in case you're not familiar with my blog post on the subject, please check out Building a commercial grade lisp plugin installer in 5 easy steps.