Hi 啓嗣,
It appears that the issue you're encountering is related to the management of the MATLAB Runtime instance within your application. The problem arises from the use of the “using” statement in the “CallMATLAB” task, which automatically disposes of the MATLAB Runtime object when the block is exited. This behaviour is not you are expecting if you intend to keep the MATLAB Runtime instance alive for the entire duration of your program.
To address this, you should manage the lifetime of the “MATLABRuntime” instance manually, rather than relying on the “using” statement. Here is the modified code for the Task “CallMATLAB”:
static asyncTask CallMATLAB(Task<MATLABRuntime> matlabTask)
{
try
{
dynamicmatlab =await matlabTask;
matlab.mydisp(newRunOptions(nargout: 0), "Hello, CallMATLAB!");
}
catch(OperationCanceledException)
{
// (existing exception handling)
}
}
Also, you'll need to ensure that you dispose of the “MATLABRuntime” instance properly when you're completely done with it.
static asyncTask Main(string[] args)
{
// (existing code)
try
{
// (existing code)
// Dispose of the MATLAB Runtime when done
(awaitworkflowTask).Dispose();
}
catch(Exception ex)
{
// (existing error handling)
}
}
This approach should prevent the MATLAB Runtime instance from being disposed of too early, allowing it to be reused for the subsequent function calls.
