topic Re: Is there anyway to call AutoCAD/ Civil 3D command from .Net? in Civil 3D Customization Forum

Is there anyway to call AutoCAD/ Civil 3D command from .Net?

soonhui — Wed, 13 Nov 2024 10:06:39 GMT

Not all AutoCAD/ Civil 3D command are easily discovered in the API doc. But assuming that I'm already familiar with AutoCAD/Civil 3D command at the command line, is there anyway that I can call them directly?

For example, I want to call `_AECCSETNETWORKCATALOG`. How can I do it?

Re: Is there anyway to call AutoCAD/ Civil 3D command from .Net?

sybold — Wed, 13 Nov 2024 12:31:50 GMT

SendStringToExecute

Re: Is there anyway to call AutoCAD/ Civil 3D command from .Net?

hippe013 — Wed, 13 Nov 2024 19:27:21 GMT

You can also use the SendCommand method of the AcadDocument.

AutoCAD 2025 Developer and ObjectARX Help | SendCommand Method (ActiveX) | Autodesk

You will need to keep in mind that there are differences in how the different methods get executed, asynchronous vs synchronously.

I ran tests using the _AECCSETNETWORKCATALOG command. At the end of my .NET code, I print to the command line using editor.WriteMessage. That message appears on the commandline while the dialog box for the _AeccSetNetworkCatalog is still up and active. That's my two cents.

Here is another link on the topic.

AutoCAD 2022 Developer and ObjectARX Help | Access the Command Line (.NET) | Autodesk

Re: Is there anyway to call AutoCAD/ Civil 3D command from .Net?

norman.yuan — Fri, 15 Nov 2024 23:21:08 GMT

Besides .NET API's SendStringToExecute() and COM API's SendCommand(), there is also Editor.Command()/Editor.CommandAsync() one can use to execute a built-in command. Unlike SendStringToExeute()/SendCommand() that run asyncly, Editor.Command() runs synchronously (but only in CommandContext).

However, not all built-in AutoCAD commands, especially C3D commands, have command-line version, and those commands would call up UI/dialog box, which would hold up the execution and wait for user interaction.

So, in general, the simple answer to your question is, yes, your execute commands from .NET API code, but many commands would not be able to continue/finish if the commands do not have a pure command-line version.