Issues running commands in a separate shell

Hello,

We are writing a C# app that needs to talk to a system running Dropbear SSH running on ARM.

We cannot use the SSH.Net RunCommand() API directly because the system requires a separate shell - due to security concerns.
Attempting to use RunCommand, the call just hangs and eventually times out.

So, we are now calling CreateShellStream() and then using ReadStream() and WriteStream() to send commands via the Shell.

This seems to work somewhat ok, but we have some concerns:
(1) Performance - after calling WriteStream(), we are calling stream.Expect()
to know when the command is complete so we can look at the results
This is noticeably slower than calling the same commands manually from a PuTTY session -
is there a better way to handle this?
(2) Command Result Processing - not clear if a command succeeds or not
after we read the output stream, we have the text from stdout,
but we have to manually parse it to see if we think the command succeeded or not
is there any way to get the command result as an integer (0 meaning success)?

thanks for any suggestions -dennis

Iniziare esaminando gli entry point RunCommand(), CreateShellStream(), ReadStream(), WriteStream() ed Expect() menzionati nel report. Determinare se il workflow con una shell separata può esporre lo stato di uscita dei comandi ed evitare il ritardo segnalato; l’issue non indica file o test, quindi è necessario chiarire l’ambito e i criteri di completamento.