Raise an event with no arguments from a COM server to be consumed by a COM client

Question

In VB.net I can declare and raise an event like this
Public Event SomeEvent()
Public Sub SomeMethod
RaiseEvent SomeEvent()
End Sub
I need to work out how to do this in c# however all of the examples of raising events include event handlers.  This won't work for me as I am raising this event over a COM interface, and so I can't send eventargs or non basic types through the interface
to the client application.
In my previous question it was suggested that I use Action and do the following
public class MyClass
public event Action MyEvent;
public void RaiseMyEvent() {
if(MyEvent != null) {
MyEvent();
MyClass myObject = new MyClass();
myObject.MyEvent += () =>
//handle...
myObject.RaiseMyEvent();
However when I tried this over the COM interface I got the following error
An exception of type 'System.InvalidCastException' occurred in AdtakerInterfaceSampleCsharp.exe but was not handled in user code
Additional information: Unable to cast object of type 'System.__ComObject' to type 'System.Action'."
The reason that I need to do this is that I am registering application A on the running object table so that I can use
Marshal.GetActiveObject in Application B to attach to the currently running process.  This is currently working fine for one way communication, however I need to be able to raise events from Application A that will be received by Application B.

Answer 1

@CoolDadTX -That's because I've written com servers in the past using VB.net, however they were not registered with the Running object table.
 What I'm trying to do in this case is have an application that will be started by the user, and then they will start another application written in .Net to connect to that first application.  The reason for this is that we have an application
written in an old version of smalltalk that doesn't seem to support getObject but can create an IUknown, and we already have base classes to attach to COM objects written in .Net.  As this new application needs to be started first it can't be tightly
coupled to the legacy application, so we are trying to register the new application and then connect a Dotnet Client that is being started through a  COM Interface from the legacy application.  I know it's convoluted but we need to keep the legacy
application alive for a bit longer while we rewrite it as an add-in for the new application.
The article that you linked to has been very helpful on the server side, but do you have any ideas as to how I can connect the sink on the client side in C#?