FAQ: Why Do My Custom Programs Not Work in the Latest Release?

Changes might be required to your AutoLISP or VBA programs that were created for AutoCAD 2015-based or earlier products if they utilize password protection or render presets. Programs that use the SendCommand method from the AutoCAD Object library may also need to be updated to use the SendCommand or PostCommand methods based on if the string should be executed asynchronously or synchronously.

Managed .NET and ObjectARX programs will need to be updated and recompiled before they can be executed in the latest release if they were created for AutoCAD 2014-based or earlier products. Programs that utilize password protection or rendering presets will need to be updated to work correctly with an AutoCAD 2016-based product.

If you are having problems with your custom programs, verify that they do not use any of the commands or system variables that were deprecated or changed for the release. You will also need to make sure that your custom programs can locate any required support files, blocks, or other resources. Verify that the required support search paths are included in the Files tab of the Options dialog box.

Note: Starting with AutoCAD 2014-based products, custom applications must work under secure mode; when the SECURELOAD system variable is set to 1 or 2. When operating under secure mode, the AutoCAD-based product is restricted to loading and executing files that contain code from trusted locations; trusted locations are specified by the TRUSTEDPATHS system variable. For more information, see About Protecting Against Malicious Code.

If you still cannot resolve the problem, contact the original vendor of the custom programs to help identify the problem and required solution.