 |
Experts on Demand
Is it safe to use a .NET system.timer declared with events in a COM interop application?
I have an app with this implementation. Everything works until I attempt to close the app, then the CPU spikes and so on. The only way to solve the problem is to kill the process. (The program was closed, but is still in memory). I have tried delegates, registering interfaces, among other possible solutions. My platform is Win2k (the app works in XP), and the language I'm using is VB.NET. Thank you for any feedback you can offer.
QUESTION POSED ON: 15 APR 2005
QUESTION ANSWERED BY: Samuel Matzen
There are always potential issues with timers because they can fire and cause methods to be called that interfere with the primary thread. But I suspect his is not your problem. I suspect you are creating and showing forms somewhere that are not getting destroyed when the main form exits. To solve this make sure all of your forms are explicitly created and destroyed.
|
|
|
|
|
|
|
|
| TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of . |
|
| |
All Rights Reserved, , TechTarget |
|
|
|
|
|
