Hi,
I have C# dll called in a VB application. And this C# dll
is multithreaded, has two threads sleeping, suspended or
running.
When the VB application exits I "Interrupt" and "Abort"
these threads. I think that these threads don't exit,
because I see the Interop dll & C# dll loaded in memory if
viewed in the Process Viewer. More over when I close the
VB IDE, I get an error message reading "Memory could not
be read". And this error message pops up only when using
the multithreaded function in the C# dll and it does not
come if we use any other function in the C# dll.
And the question here is:
Is there any other better way to clean up the
multithreading and C#, VB interop?
And how can I stop this error message popping up?
Any help will be appreciated.
Thanks
Jana
I have C# dll called in a VB application. And this C# dll
is multithreaded, has two threads sleeping, suspended or
running.
When the VB application exits I "Interrupt" and "Abort"
these threads. I think that these threads don't exit,
because I see the Interop dll & C# dll loaded in memory if
viewed in the Process Viewer. More over when I close the
VB IDE, I get an error message reading "Memory could not
be read". And this error message pops up only when using
the multithreaded function in the C# dll and it does not
come if we use any other function in the C# dll.
And the question here is:
Is there any other better way to clean up the
multithreading and C#, VB interop?
And how can I stop this error message popping up?
Any help will be appreciated.
Thanks
Jana