MATLAB: Less Offensive Exception Handling

exceptionhandlingMATLABnet

Hello! We are developing a .NET WPF application which is working with MATLAB R2015b in a toolchain. We implemented (in our application) a global exception handler for logging the error. It works, if we start our application without MATLAB. But this routine is never called, because MATLAB catch the exception bevore this global routine handler got the exception.

Is there a way to change it (so at least we can see/log the error)?

Best Answer

Correction: The initialization of the handler is placed in App.xaml.cs was wrong. Better is to place it in the "Builder"-class, which return an instance to the Window. I solved the problem by changing the kind of initialization:

Application.Current.DispatcherUnhandledException += Current_DispatcherUnhandledException;

instead of

AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(DispatcherUnhandledException);

And the method:

private void Current_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
{
  //Do some things
}

Related Solutions

MATLAB: Matlab::data::ArrayFactory exception: “attempted to assign clientFactoryFuncPtr twice to different values”

Contrary to our first assesment, also the generated sample code does not work flawlessly: It just fails silently, because of the structure of the sample script, and because exceptions are not caught in the function called by runMain().

After further investigation we now see that the behavior described above is introduced by linking to "libMatlabDataArray.so" of the installed Matlab Runtime. Linking against the library provided by the Matlab installation seems to solve the issue.

MATLAB: Can the Assembly not be found when deserializing a .NET object in MATLAB 7.10 (R2010a)

Please note that the behavior described above is not a limitation of MATLAB. It is in fact expected behavior of the .NET framework.

By default when deserializing an object, the .NET Framework will only look for the required Assembly in the "EXE directory"; it will not even look for already loaded Assemblies.

To make the deserialization work, you will thus need to either:

1. Place myAssembly1.dll in the $MATLABROOT\bin\[win32|win64] directory, or

2. Implement your own ResolveEventHandler for the AppDomain.CurrentDomain.AssemblyResolve event in myAssembly2. So for example in the constructor of myClass2 add:

AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(CurrentDomain_AssemblyResolve);

To register your own ResolveEventHandler called CurrentDomain_AssemblyResolve. This CurrentDomain_AssemblyResolve could look like:

System.Reflection.Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
      System.Reflection.Assembly ayResult = null;
      string sShortAssemblyName = args.Name.Split(',')[0];
      System.Reflection.Assembly[] ayAssemblies = AppDomain.CurrentDomain.GetAssemblies();
      foreach (System.Reflection.Assembly ayAssembly in ayAssemblies)
      {
          if (sShortAssemblyName == ayAssembly.FullName.Split(',')[0])
          {
              ayResult = ayAssembly;
              break;
          }
      }
      return ayResult;
}

This particular ResolveEventHandler will allow you to use already loaded Assemblies when deserializing objects.

Best Answer

Related Solutions

MATLAB: Matlab::da​ta::ArrayF​actory exception: “attempted to assign clientFactoryFuncPtr twice to different values”

MATLAB: Can the Assembly not be found when deserializing a .NET object in MATLAB 7.10 (R2010a)

Related Question

MATLAB: Matlab::data::ArrayFactory exception: “attempted to assign clientFactoryFuncPtr twice to different values”