Why does System.Diagnostics.Process not work? Matlab and .Net-Framework Problem
9 ビュー (過去 30 日間)
古いコメントを表示
Hello Community,
i am trying to use some Functions that use System.Diagnostics.Process (e.g. sim3d.Engine.engine, Vehicle Dynamics Blockset). This used to work on my Notebook and Desktop. However since i updated one PC to the newest Windows Version 1903, functions with System.Diagnostics.Process dont work on this machine anymore. I assume it has something to do with the .Net Framework. I tried a clean re-install of windows 10, but the problem persists. I compered both .Net Installations (regedit) and they seem to be identical.
This is the actual function i want to use:
>> sim3d.Engine.engine
Error using sim3d.Engine/setup %this should be red (error)
Invalid default value for property 'engine' in class 'sim3d.Engine': %this should be red
No method 'Start' with matching signature found for class 'System.Diagnostics.Process'. %this should be red
Error in sim3d.Engine %this should be red
And this is the general approach to run System.Diagnostics.Process
A = NET.isNETSupported
notepad = System.Diagnostics.Process();
notepad.StartInfo.FileName = "notepad.exe";
notepad.StartInfo.UseShellExecute = false;
notepad.StartInfo.CreateNoWindow = true;
notepad.Start;
The result:
A =
1
No method 'Start' with matching signature found for class 'System.Diagnostics.Process'. %this should be red (error)
The actual function i want to use: %this should be red
So what exact Version of the .Net-Framework is required for Matlab? Maybe the Problem is the relativly new Framework 4.8? Or could it be that the path /variable to the .Net directory is messed up? Im out of ideas.
Thanks, Mathias
0 件のコメント
採用された回答
Mathias Voigt
2019 年 9 月 27 日
3 件のコメント
Martijn
2020 年 1 月 30 日
Note that the original question discussed two issues, clearly related, but which were eventually addressed in two separate bug reports:
1. In certain places like Simulink 3D Animation, System.Diagnostics.Process.Start was used internally, this is discussed in:
2. If you yourself are directly working with System.Diagnostics.Process.Start, see:
Which also discusses a workaround: Use Start(p) instead of p.Start()
その他の回答 (0 件)
参考
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!