We’ve received a few common questions recently from developers using AcCoreConsole (which Balaji blogged about here, and Kean here). Here are the two questions (and answers kindly provided by a member of our AutoCAD development team) …
Q1: What ObjectARX libraries can I link to for my DLL to load in to AcCoreConsole (or other ‘AcCore enabled’ product that Autodesk may ship in the future)?
A1: Here’s the list of libs that you can link with when you are developing an ARX, CRX or DBX app -
LIBRARY | OK in DBX | OK in CRX | OK in ARX |
ac1st19.lib | YES | YES | YES |
acdb19.lib | YES | YES | YES |
acdbmgd.lib | YES | YES | YES |
AcDbPointCloudObj.lib | YES | YES | YES |
acge19.lib | YES | YES | YES |
acgiapi.lib | YES | YES | YES |
acismobj19.lib | YES | YES | YES |
AcMPolygonObj19.lib | YES | YES | YES |
AcSceneOE.lib | YES | YES | YES |
axdb.lib | YES | YES | YES |
rxapi.lib | YES | YES | YES |
acbr19.lib | YES | YES | YES |
acgex19.lib | YES | YES | YES |
AdImaging.lib | YES | YES | YES |
AdIntImgServices.lib | YES | YES | YES |
AecModeler.lib | YES | YES | YES |
AsdkHlrApi19.lib | YES | YES | YES |
acapp_crx.lib | NO | YES | YES |
AcCamera.lib | NO | YES | YES |
accore.lib | NO | YES | YES |
AcFdEval.lib | NO | YES | YES |
AcPublish_crx.lib | NO | YES | YES |
acad.lib | NO | NO | YES |
acapp.lib | NO | NO | YES |
AcFdUi.lib | NO | NO | YES |
acModelDocObj.lib | NO | NO | YES |
AcTc.lib | NO | NO | YES |
AcTcUi.lib | NO | NO | YES |
acui19.lib | NO | NO | YES |
AdApplicationFrame.lib | NO | NO | YES |
adui19.lib | NO | NO | YES |
aNav.lib | NO | NO | YES |
aseapi19.lib | NO | NO | YES |
asiapi19.lib | NO | NO | YES |
Checking a .NET DLL is easier – you just remove the reference to AcMgd.dll.
Q2: How do I register my CRX app for demand loading (e.g. on command invocation)?
A2: You register them exactly as you would for an AutoCAD app. The only difference is that AcCoreConsole will not load an ObjectARX DLL with the extension ‘ARX’. You have to rename the extension to ‘CRX’.