Comments on: Windows CE Task Manager Sample App http://blog.theroyweb.com/windows-ce-task-manager Sorry, never heard of the guy Tue, 03 Aug 2010 16:36:28 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Mbg http://blog.theroyweb.com/windows-ce-task-manager/comment-page-1#comment-39 Mbg Wed, 23 Dec 2009 07:00:58 +0000 http://www.theroyweb.com/blog_priv/?p=26#comment-39 This might sound stupid, but why don't you have App A start App B (step 2) and then have App A close itself? So, in 2 (VB.Net syntax): Process.Start(PathToAppB & "AppB.exe", "Parameter 1") Me.Close() If you start an app with the above command, that app will run independently from the starting app. Closing the creating app (say, A) will not terminate the new app (say, B). Good luck. This might sound stupid, but why don’t you have App A start App B (step 2) and then have App A close itself?

So, in 2 (VB.Net syntax):
Process.Start(PathToAppB & “AppB.exe”, “Parameter 1″)
Me.Close()

If you start an app with the above command, that app will run independently from the starting app. Closing the creating app (say, A) will not terminate the new app (say, B).

Good luck.

]]> By: Ali http://blog.theroyweb.com/windows-ce-task-manager/comment-page-1#comment-33 Ali Wed, 21 Oct 2009 05:13:04 +0000 http://www.theroyweb.com/blog_priv/?p=26#comment-33 Hi, currently I'm creating 2 applications (app A and B) for Windows Mobile 5.0 and using Compact Framework 2.0. App A is the main application and B is the sub application. Below is the flow: 1. Start app A. 2. App A will start app B. 3. App B will do some process. 4. App B will kill app A. 5. App B will patch/upgrade app A. (ala update manager) 6. App B will restart app A. 7. App B will exit. Now I'm stuck in killing app A. I did tried using OpenNETCF ProcessEntry Kill() function. When calling Kill(), it made the device crash. I did tried using the SendMessage(hWnd, WM_CLOSE, 0, 0) funct where WM_CLOSE will have the ProcessEntry.ProcessID value and I didn't assigned any value to hWnd variable. But it didn't terminate app A. Did I assign the wrong value? I also did tried using Process.GetProcessById(processEntry.ProcessID).CloseMainWindow(), but failed as GetProcessById only accepts int32 value. Note that processEntry.ProcessID value is larger than int32 value. Could you help me in killing app A through app B? Thanks. Hi, currently I’m creating 2 applications (app A and B) for Windows Mobile 5.0 and using Compact Framework 2.0. App A is the main application and B is the sub application.

Below is the flow:
1. Start app A.
2. App A will start app B.
3. App B will do some process.
4. App B will kill app A.
5. App B will patch/upgrade app A. (ala update manager)
6. App B will restart app A.
7. App B will exit.

Now I’m stuck in killing app A. I did tried using OpenNETCF ProcessEntry Kill() function. When calling Kill(), it made the device crash.

I did tried using the SendMessage(hWnd, WM_CLOSE, 0, 0) funct where WM_CLOSE will have the ProcessEntry.ProcessID value and I didn’t assigned any value to hWnd variable. But it didn’t terminate app A. Did I assign the wrong value?

I also did tried using
Process.GetProcessById(processEntry.ProcessID).CloseMainWindow(), but failed as GetProcessById only accepts int32 value. Note that processEntry.ProcessID value is larger than int32 value.

Could you help me in killing app A through app B?
Thanks.

]]>