System::EventHa ndler and event function "Sender" relation?

[Sin]

Hello,

I'm currently toying around with using a VB.NET interface in a VC.NET
program and I've come across somewhat of a problem. I found a workaround but
I figure I must be a bit off cause it feels weird.

I have two projects. One is a simple VC console program. The other is a VB
Class Library project (DLL) in which there is a form (Form1) on which there
is a button (Button1) and a textbox (TextBox1). Both these controls are
public.

I've added an event on the click in VB that simply shows a messagebox. I've
done the same in VC, adding an event at runtime. Here's my code :

__gc struct Form1_Events {
static void Button1_Click(S ystem::Object *sender, System::EventAr gs *e) {
Windows::Forms: :Button *but= static_cast<Win dows::Forms::Bu tton
*>(sender);
MyVBInterface:: Form1 *frm= static_cast<MyV BInterface::For m1
*>(but->Parent);
MessageBox::Sho w(frm->TextBox1->Text, 0);
}
};

int _tmain() {
MyVBInterface:: Form1 *frm= new MyVBInterface:: Form1;
frm->Button1->Click += new System::EventHa ndler(frm,
Form1_Events::B utton1_Click);
frm->ShowDialog() ;
return 0;
}

Initially, I expected the sender param of Button1_Click to be a pointer to
my form (which is what I pass when I create the handler!) but it's not so, I
get a pointer to the button...

I don't really like the 'trick' I used which gets the parent of the button
to get access to the form. I also found out I cannot put frm global, so
right now I *have* to use this trick to access the form.

What would be the prefered way to handle this problem?

Thanks alot,

Alex.