Prev: How to use Early late timing recovery block in simulink
Next: Newton-Raphson
From: Rob Slazas on 18 Jan 2010 06:25
Has anyone else had to use a 3rd party .NET assembly in a MATLAB script, and then make it into a stand-alone application using the Compiler? I'm having difficulty getting the Compiler to use the .NET assembly correctly. Here are the specifics:

When running the MATLAB script directly, I just need to precede it with the following line to include the .NET assembly:
>NET.addAssembly('c:\foo.dll');
Then the script can execute correctly when it calls on foo.dll 's .NET components.

The trouble comes when I try to compile this script to deploy to other machines that do not have MATLAB. Note that I am not using the .NET builder, but the MATLAB compiler. The .exe produced does not work since it cannot access the .NET components of foo.dll. So far I have tried adding it as an 'include', which is wrong since foo.dll is not a c library. Any ideas about obscure compiler switches that could do this?

Thanks in advance for any ideas,
Rob
From: Rob Slazas on 18 Jan 2010 07:24
Cheesy work-around:

I just tried writing a wrapper script 'wrapper.m' that has two lines, and compiled it successfully:
>NET.addAssembly('c:\foo.dll');
>main.m;

This works, but my original question still stands since I would like to know the proper way to use the .NET assembly with the compiler. Hopefully someone has done this before.
 | 
Pages: 1
Prev: How to use Early late timing recovery block in simulink
Next: Newton-Raphson