c# activeX controller hanging tstcon32's exit

[jab_joe]

Hi,

I've searched the internet high and low for someone else having had
this problem and solved it. But every c# activeX controller sample I
look at shared the same problem. And I can find no mention of it any
where.

When any c# activeX controller is dropped into tstcon32.exe,
tstcon32.exe won't exit. It just hangs in the background. Dispose is
never called.

When the same c# activeX controller is hosted in 3dsMAX through a
MAXScripts rollout, Dispose is only called on 3dsMax's exit. So if you
keep opening and closing a window with the rollout, you will get all
the Disposes called only on 3dsMax's exit. Which means closing the
window isn't clearing the c# activeX controller from memory. Each
openning of the window is creating a new one. Not really a tenable
position....

Any ideas? I've added a destructor (because I understand that is
Finalize in c#), but that flows the same calling pattern. I.e no call
in tstcon32 and only called on exit for 3dsMax.

Surely someone else has hit this, it's in every c# activeX controller I
have seen. What is this and how do I get past it?
I'm not out of ideas, but getting close now.....