Richard
We double checked the InvokeRequired, which is mainly used when the server
sends event messages for that client. The problem is that it may happen on
any control, absolutely arbitrary. For instance, it happened to myself when
clicking on the boolean drop down in a property grid, where absolutely no
code is executed except the standard internal propGrid bool dropdown
handler. At this time, no timers, background threads or call backs were
running/expected, no events received from the server, the app was in idle
state. And it only happens on a click or keystroke, never by itself. Does
this give you some more ideas what else we could look for?
Thanks, Urs
"Richard Blewett [DevelopMentor]" <ri******@develop.com> schrieb im
Newsbeitrag news:%2****************@tk2msftngp13.phx.gbl...
Hi Urs,
The only time I've seen this behavior is with a background thread calling
the UI directly. I know you have said you use the
InvokeRequired/BeginInvoke pattern everywhere, but it may be worth double
checking just in case.
Regards
Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<eS**************@TK2MSFTNGP15.phx.gbl>
Hi
we encountered a strange problem in our Windows client. It sometimes
(fortunately rarely) just disappears with all open windows, without
throwing
an exception, either after a click on any control or a keystroke, although
the app makes 100% use of structured exception handling, including all
event
handlers and Main(). For threaded ops, we make strict use of
InvokeRequired.
No WinAPI calls are made, no unmanaged code is used in this client.
What could cause a 100% .Net based app to vanish without warning?
