Hi all, i´ve posted something similar to [OT] before, but it seems to get more interesting (at least for me), so I switched to this list.
I´ve have a nice application (c#), where I watch a list with an event. And every time this list gets a new object, the event handler will remove it and pass it to another thread. This thread will execute this commandobject, and suspend it self afterwards. My event handler of course resumes the event after passing the command object. The problem is: When I do all this in a debugging build (launched from VS) my task manager tells me that my app uses all available CPU cycles (even when thread is already suspended). When I do all this with a release build (launched from desktop (you know: click-click ;-)) then task manager is maybe bored, cause it shows up 0 % used. Does someone have any idea about that? Is it because of the attached debugger? Or VS.NET?? tia alois You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
