Launch accoreconsole as process from vb.net not working in AutoCad 2022

[austin.bryanD2AEJ]

I have a VB console app that launches AutoCad's coreconsole as a process.  It includes an argument that is a script which loads and calls autolisp programming.  It works just fine with AutoCad 2018 but not on 2022.  Below is the VB code and the script file.  Suggestions on why 2022 is not cooperating?  Note that the trusted paths are set just the same in 2018 and 2022.  SECURELOAD is set to 0.

Dim ACC_Process As Process
Dim ProcessProperties As New ProcessStartInfo

ProcessProperties.FileName = "C:\Program Files\Autodesk\AutoCAD 2022\accoreconsole.exe"

ProcessProperties.Arguments = " /s " & "C:\temp\ACCoreconsoleScript.scr"

ProcessProperties.WindowStyle = ProcessWindowStyle.Minimized

ACC_Process = Process.Start(ProcessProperties)

Script:

(load "c:\\acadcode\\ccm.lsp")
(ccm)

[Ed__Jobe]

It doesn't help at all when you just say something isn't working. Imagine you are us, and describe it.

[kerry_w_brown]

Have you played with the  LEGACYCODESEARCH  system variable ?

[austin.bryanD2AEJ]

Thanks for your quick reply.
Let me try and be a little more thorough.
When using 2018 the process launch&script opens the coreconsole window, a variety of autolisp programming runs and concludes with a Quit statement that closes the coreconsole. The only change I made to the VB code was changing the year of AutoCad from 2018 to 2022.
ProcessProperties.FileName = "C:\Program Files\Autodesk\AutoCAD 2022\accoreconsole.exe"
The coreconsole still opens (I can see it using the Task Manager and looking at background processes) but the script does not appear to execute and subsequently the autolisp code does not run.
So the real question is, what is stopping the script and/or autolisp from running?
Two observations:

1. If I launch the accoreconsole.exe application manually and type in the lines shown in the script, everything runs as it should in 2022. The autolisp code is loaded and the programming runs to completion.
2. If I open AutoCad, load my autolisp code (i.e. Load Application) and make the function call at the command line, again everything runs to completion.
The behavior I see is what I would expect if there was an issue with trusted paths (i.e. error when trying to load an application from a path not included in my trusted paths). However, the trusted paths are the same in both 2018 and 2022. Additionally I set SECURELOAD to 0 in order to remove that as a possible source of error.
I suppose what I am looking for is any other settings that might be prohibiting the loading or running of autolisp from an external source (VB).
I am officially struggling now. I am happy to give you whatever support I can if it means I can get this off my plate.
Austin

[austin.bryanD2AEJ]

Thanks for your reply
I tried with LEGACYCODESEARCH both on and off. The results were the same.
I do call out the entire path to the autolisp code in the script:
(load "c:\\acadcode\\ccm.lsp")

[Norman_Yuan]

@austin.bryanD2AEJ 

When you say the lisp is loaded from one of "trusted paths", You do realize the trusted paths are associated to an user profile (e.g, different user profile can define different trusted paths). So, in order for AutoCAD to trust a path, you need to make sure AutoCAD runs with the user profile that defines that path as "trusted". Therefore, you should add "/p [profileName]" to the ProcessStartInfo's Arguments property, besides  "/i [drawing path]" and "/s [script]".

[austin.bryanD2AEJ]

Thanks for your reply. I was hopeful but this did not seem to help. Both 2018 and 2022 were using the default <>. I included this in my arguments as you suggested. I also tried making a new profile with the same trusted paths. I added that new profile as an argument. No luck.

[austin.bryanD2AEJ]

Hi All

Thanks for all your input.  As it turns out, this autolisp statement was causing the crash:

(VLA-object "ActiveX objects")

Fortunately, I do not need the related code anymore.  Problem solved with delete button.

Have a great day.