One other thing would be to check to see if your process has actually
exited using remote process viewer, your app could still be running
but with no main window visible (for whatever reason) and it will not
show up in the running programs list.

Matt

On Nov 8, 1:17 pm, Jesse Houwing <jesse.houw...@newsgroup.nospam>
wrote:

On Nov 8, 7:17 am, Jesse Houwing <jesse.houw...@newsgroup.nospam>
wrote:

Jesse,

I am using a solution like the one explained in
http://msdn.microsoft.com/msdnmag/issues/04/12/netcompactframework/default.aspx#
bottom,
under the section "Bad, Wicked Dialogs". That solution works fine with
both WM5 and WM6. If I do not use that trick and just a plain
ShowDialog() then I get each form in my application listed in the
Running Programs List, on both platforms. I cannot understand the
behavior I explained above. Somehow the child form was closed or
removed and the parent form was not informed of it. The parent still
thought the child was opened that's why it was not responding. But I
could not see any of them (parent & child) listed as running, so it is
as if they both were closed (when I tried closing my app, I clicked
many times the Exit link to my app) but for some reason the Parent
form stayed in display unresponsive.

We had a user who was testing our application in WM6, the Sprint HTC
smartphone. He encountered this problem after his telephone locked
itself (his company uses some locking mechanism in the telephones that
is related to Pocket Outlook). After he unlocked the phone (it got
locked when he had an instance of our app. running and he was not
using the phone for more than 15 minutes) our application screen was
frozen and he could not even try to restart a new instance of the
same. This is a non-technical user who has no idea on how/where to
check for all the current processes running, he did not even know how
to soft/hard reset his device.

Another user, a programmer in my company claims that he got the frozen
form after leaving his device idle and running our app over the night
on his desk. When he came back the following day to work, the phone
was off, he turn it on and the problem was there.

I posted this message yesterday and before I left home I left my
smartphone running my app. Today in the morning I found my phone off,
I turned it on, my app was there running BUT not frozen. So you
figured.

Is this because of WM6? or is this because of using a smartphone? All
our users running on WM5 use handhelds, not telephones. For WM6. we
have only tested on smartphones, never on handhelds running WM6. Also
the smartphone has a detachable keyboard. Although yesterday when I
encountered the problem I was not using the keyboard at all.

If you can find any notes or comments about this, I'll apprecite to
get them all.

Thanks!