Thread Subject: Interfacing Matlab with C#

I have a program that will be passing data to a C# script.
C# will then be modifying the data and I need it to be sent
to Matlab. Matlab will perform some function and then pass
the data back to C#. This all needs to be done in real
time, and not necessarily on the same computer. So how do
I pass data from C# to Matlab? I've been reading a lot of
help files in the Simulink and Real Time Workshop
categories, but I can't piece it all together to get a
useful answer. Most of my searches online have led to
people wanting to call C# from Matlab or convert their
Matlab files to C# or things like that. I want to have a
stand-alone Matlab file (probably a Simulink model) that
just sits there waiting for information, and have the
information coming from a separate C# program. Is this
doable and how?

I've done this by writing an IDispatch COM interface around
the C# method and then invoking it in MATLAB through DCOM
with activexserver.

"Daniel " <cowmaster6@yahoo.com> wrote in message
<fmleji$33i$1@fred.mathworks.com>...
> I have a program that will be passing data to a C#
script.
> C# will then be modifying the data and I need it to be
sent
> to Matlab. Matlab will perform some function and then
pass
> the data back to C#. This all needs to be done in real
> time, and not necessarily on the same computer. So how
do
> I pass data from C# to Matlab? I've been reading a lot
of
> help files in the Simulink and Real Time Workshop
> categories, but I can't piece it all together to get a
> useful answer. Most of my searches online have led to
> people wanting to call C# from Matlab or convert their
> Matlab files to C# or things like that. I want to have a
> stand-alone Matlab file (probably a Simulink model) that
> just sits there waiting for information, and have the
> information coming from a separate C# program. Is this
> doable and how?

Register your C# as COM library. Right click on your
project, go to Build and check the box "Register as Com
Interop". Then create an interface for the methods you want
to expose to COM and add the following attributes. A GUID
can be created in VS2005 (see Tools)

[Guid("xxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx")]
[ComVisible(true)]
public interface IComInterface
{
      char SeparationCharacter { get;}

      bool LogOff(string userID);
}

Implement the interface on a class and set the following
attributes on this class

[ProgId("MyCom.1.0.0")]
[ClassInterface(ClassInterfaceType.None)]
[Guid("xxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx")]
[ComVisible(true)]
public class ComClass: IComInterface
{
     public char SeparationCharacter
        {
            get
            {
                return '#';
            }
        }

        public bool LogOff(string userID);
        {
            return true;
        }

}

Create an instance of this class using actxserver:

>h = actxserver('MyCom.1.0.0')]

h.get will receive all setter properties:

->SeparationCharacter: 35

separationCharacter = h.SeparationCharacter

Invoke will return all methods

>h.invoke

->LogOff = bool LogOff(handle, string)

The method can be invoked like this:

>success = h.LogOff('me')

->success = 1

I hope this is useful

Jaco de Groot

.. Many questions spring to mind, but one is 'How would
Matlab know of the new DLL?'

This article is very helpful.
http://www.codeproject.com/KB/dotnet/matlabeng.aspx

I've developed applications using solution #1 and it works
perfectly.

Thank you, Wagner, but the challenge is to call C# from
Matlab, not Matlab from C#.