Why does Matlab crash when I try to access .NET 6.0 (core)?

Note: Workaround is to remove .NET 9.0 from PC to resolve conflicts with 6.0.

This might be a .NET issue as a whole, but I only see it using Matlab, so I am posting here to help others out facing the same issues.

I have a .dll from one of the groups I work with for communicating to our devices. The .dll was built in .NET 6.0 (core) (x64). I have been able to use it in the past in Matlab, but have now run into issues since installing Visual Studio 2022. It was discovered that Matlab would reference the most recent installation of .NET (9.0 in my case) which was installed by VS 2022. When I set "core" as the environment in Matlab (dotnetenv("core")), I would then make the .NET assembly visible to Matlab using NET.addAssembly("insert path here"). When Matlab got to this step, it would buffer for about 10 seconds then crash immediately with no crash report. Getting help from my local IT, we pin pointed it to the .NET 9.0 install causing the problem.

To get around this, you can either uninstall 9.0 or set up an environment variable in your system properties called "DOTNET_ROOT" that can force a path to be referenced.

So I would like to ask if anyone else has faced this issue in Matlab? Is it an unexpected error that needs an error handle? I am naive to .net, and really only know the particular dll I interact with to do my methods, etc.

Answer 1

[aditi bagora]

Hi @Matthew,

I have faced the same issue. I found that this issue is specific to .NET 9.0 and does not originate from MATLAB.

After installing Visual Studio 2022, your system updates to the latest version of .NET, which is .NET 9.0 and MATLAB by default, uses the latest version of .NET installed on your system(refer the documentation below), this can lead to a crash. Therefore, uninstalling .NET 9.0 or setting "DOTNET_ROOT" path is solving the issue.

https://www.mathworks.com/help/matlab/matlab_external/system-requirements-for-using-matlab-interface-to-net.html#:~:text=MATLAB%20uses%20the%20latest%20version%20of%20.NET%20found%20on%20your%20system.

I hope this helps!

[Matthew]

Hi @aditi bagora, thanks for providing feedback. I went with the DOTNET_ROOT option on my setup. Glad to see I wasn't doing anything inherently wrong on my end.

@埃博拉酱 thank you. Looks like they aim to have Jan 2025 as a fix release for the bug.

Answer 2

[埃博拉酱]

This is a known dotnet issue already submitted to Microsoft by MathWorks staff.

20241218

An easier workaround, from tech support:

feature("USE_DOTNETCLI2_WINDOWS", 1)

[Frank]

Hi,

it would be more helpful to post an explanation on why this workaround could helps.

What does it? How to reset?

[埃博拉酱]

@Frank I don't know. This workaround is from tech support of MATLAB internal staff. No more details are offered.

Answer 3

[Richard Scott]

I found just pasting the following code into MATLAB script editor is enough to crash MATLAB without even trying to run the script.

	asm = NET.addAssembly('System.Windows.Forms');
	import System.Windows.Forms.*
	MessageBox.Show('Simple Message Box');

also running the following line would be enough to crash MATLAB.

    NET.isNETSupported

Windows Event Log contains the unhandled exception data. In additiona to any fix that Microsoft may implement, MATLAB may want to try catch the unhandled exception for a more gracefull user experience.

My workaround was to edit the config file as described in the MATLAB help section "System Requirements for Using MATLAB Interface to .NET". Specifically I changed

"rollForward": "LatestMajor"

to

"tfm": "net6.0",

With the complete file as follows:

{
  "runtimeOptions": {
    "tfm": "net6.0",
    "framework": {
      "name": "Microsoft.WindowsDesktop.App",
      "version": "6.0.0"
    }
  }
}